Get the highlights in your inbox every week.
Interview with Jeremy Edberg from Netflix
The open source culture of freedom and responsibility at Netflix
His adventure started in college with Slackware, lead him to Sendmail, then eventually to Reddit, and now his career is streaming at Netflix. Jeremy Edberg is a Reliability Architect at Netflix and will be speaking at DevNation in April 2014 in San Francisco, California.
We decided to catch up with Jeremy and ask him a few questions in advance of his talk. I'm really looking forward to learning more about the culture of Netflix which Jeremy describes as "Freedom and Responsibly." How that ties to open source? I'm curious. But I get the impression that breaking things and fixing them quickly is part of that culture and might include a "you break it, you fix it (quickly)" kind of attitude.
In this interview, I ask Jeremy how he applies open source outside of technology and what he wishes were more open in this world. His answers might surprise you.
How did you got involved with open source?
My first experience with open source was in college (because college is a time for experimentation, right?). It stemmed from me wanting to have a robust operating system with a 32bit kernel, but not wanting to pay for WindowsNT. I picked up a copy of Berkeley's Slackware distribution that was custom created for dorm residents (which of course was only possible because it was open source). The journey just expanded from there. I started working for Berkeley's housing group, where our entire infrastructure was based on open source components like Red Hat, perl, Apache, and so on.
My first full time job was with Sendmail, which was all about open source obviously. They were one of the first businesses trying to make a business out of open source software. It was there that I started using FreeBSD and was actually in charge of the web server for sendmail.org for a while.
After that I would occasionally share code on my website or other places. Once GitHub came along, I tried to put useful utilities that I wrote up there. A few are still there.
My first commit to a public open source project actually came many years later when I made a change to the boto library, which is a Python library used for interacting with Amazon Web Services.
What will you discuss at the DevNation conference (without giving too much away)?
At DevNation, I will be discussing how Netflix's culture of freedom and responsibly intertwines with how we operate our service. I'll be talking about our Service Oriented Architecture and the various steps we take to build anti-fragile systems through constantly trying to break things.
Tell us more about the open source projects you work on at Netflix.
I don't work directly on open source at Netflix, but I work closely with many of the teams that produce open source and help spread the word.
What aspects of open source do you apply to your interests outside of technology?
I'm a big fan of sharing knowledge in general, which is why I like to present at conferences. At the end of the day, open source is all about sharing human knowledge and moving the planet forward, and I think we can do that with a lot more sharing. Also, I recently supported an open source beehive on Indiegogo!
What's one thing in life that you wish were more open?
Medical data (well data in general but specifically medical). If there were a way to safely, securely, and privately share medical data, I think we would make massive strides in early diagnosis and curing disease. Especially if we could combine that with free genome sequencing. Imagine the possibilities if every person's symptoms and ailments, along with their genes, could be crunched through massive data systems? I'm a huge fan of the work that 23andme is doing—I wish the FDA would let them continue.