Long time no see. In the last two months a lot has happened. I interviewed at seven different tech companies for software engineering internships, I got an internship at Chef Software, I developed and deployed Lights on WA, my a capstone project, and I saw the grand canyon for the first time. So it’s been a great couple of months.
Ada Developers Academy has great selling points, but the two that definitely make it rise above the fray are the facts it is free and that there is a built in five month internship for those who go through the program. The internship is critical as it gives you real world experience at a local software company before you have to start the job application process. It also gives you the opportunity to apply and do technical interviews with the guarantee of a job at the other end before you have to do more high-stakes interviews which is amazing practice. We were all a little more than nervous for our week of seven technical interviews and knowing that at the end every person would get an internship made it a lot easier. I interviewed with a range of different companies both small and large. Some of the interviews were purely technical, some situational, some just talking about why I was interested in coding. All of my interviews were positive experiences, even though I came down with a cold and was pretty ill and could barely speak or get the ringing out of my head at the beginning of the week. Technical interviews can be scary for people coming from different fields. In a lot of cases it’s basically someone asking you a logic puzzle and watching you speak and write on a whiteboard while they judge you on how and if you solve it. There’s a lot more to it than that but it can often feel like a quiz. It’s really about how you build trust and candor with the interviewer in a short amount of time and do so in order to solve a complex problem. Some people also just like to see how you react when you draw a blank — do you panic? do you pull through? So any situation in which panic is an option can be stressful.
I ended up appreciating the interviews and to my bemusement found that the ones with harder questions and interviewers that pushed me to think more deeply about efficient solutions were the interviews I enjoyed the most. I am happy to say Chef was one of those interviews.
In order to make interviews less daunting and more silly our cohort added some little traditions to the process. We all wrote each other notes to be opened before each interview and had a costume box where we dressed up after each interview and took disposable camera photos.
About two weeks after our interviews were finished we found out our placement companies. I was overjoyed to find out I’d be interning at Chef. I had found their interview engaging and challenging, they are a remote company, they pair program, they are a DevOps company which is a deep area of interest for me, and they are Open Source.
Funny enough the morning I found out I’d be interning at Chef, I met up with one of the Adies who works there now for coffee. I am excited that two people from the program are already there as full time engineers and love the company. It has been hard to explain exactly what the company does to my family and non-tech friends (all my friends) but for most software people Chef is a leading name in DevOps or Development-Operations. They produce software for software companies that makes the deployment and configuration process easy and even fun. The only friend of mine I know in tech was very excited when I told him this is where I’d be interviewing as he handles the Chef recipes at his job. Chef is written in Ruby (yay!) and a functional programming language called Erlang. One of my goals and wishes for the next six months has been to learn a functional programming language so I’m excited for the challenge. Chef’s frontend will also be a challenge for me in learning Angular 2, which is brand new and daunting. I’ve already started to learn a little Erlang and transfer to the text-editor Vim over the last week and it’s a whole new world to me. Our cohort has three weeks starting tomorrow to “ramp up” before internships start in April. I’ll be using that time to dive into more Ruby, Chef Recipes, Erlang, and Angular before I start.
Note: I also found out last week that I was accepted as an Opportunity Scholar for Railsconf and will be attending in May! Chef is a sponsor so I hope I’ll get to see Chef employees from different parts of the country there.
Capstone Month: Lights on Washington
And all this brings us to Capstone Month. After interviews were done we quickly started working on our four-week individual projects. However daunting, capstone proved to be the most fun I’ve had at Ada (don’t get me wrong, it was all fun!) I have been incredibly impressed with all the ideas and deliveries that my cohort pulled together over these four weeks.
My project started with thinking about campaign finance in the Washington State. I wanted to make donations and candidates more transparent. So I decided to take the data from the Public Disclosure Commission, which controls campaign finance in our state, and make it more accessible and host it on my own site. Easy, right? Well, public data is a lot more complicated than that. My first big problem was that I didn’t have easy access to the data. A public records request I put it took 3.5 weeks to come through. I had to build a web scraper to get all the data from the site.
In interviews we talk a lot about space and time efficiency without any practical experience about when this might be applicable. We tend to think that it’s just for interviews that we need to know the run time of different sorting algorithms. Through working on Lights on WA I started to see the immense value in having a basic understanding of memory, space, efficiency, and algorithms. I talked some about this in the presentation I gave on our final day. The slides can be found below and the website at lightsonwa.com.
I was very proud of how Lights on WA turned out. I talked to some friends working in politics in Washington who were enthused to pass it around. I am also proud about the fact it is a civic hacking project and that I learned how to get information from the government when they are slow to deliver a public records request. I definitely want to stay connected to the open data world that I experienced a little slice of and would absolutely participate in more side projects that had to do with making our data more accessible. Finally I am proud of how much I learned about performance and data structures. I am proud that I used the resources available to me to finish and exceed my MVP. The whole process gave me a lot of confidence in my skills and made me excited to dive deeper into DevOps in the coming months.