October, 2013

devopsdearabby / Episodes / Panels — Comments Off
26
Oct 13

To Be Continued: Release Engineering Tools at Netflix

It is fitting that our first episode to be split into a TV-esque cliffhanger is with our Netflix panel! In episode 28, we discussed Netflix’s unique engineering culture; in part two, we discuss with the panel the dynamics of how Netflix develops its release engineering tools, Netflix’s cloud prize, configuration management vs. baked potatoes, what percentage of the Internet Netflix actually uses at peak, plus the panel’s guilty (and possibly embarrassing) Netflix pleasures; find out what they are and more when we wrap up:

To Be Continued: Release Engineering Tools at Netflix

Join J. Paul Reed, aka @SoberBuildEng, Youssuf El-Kalay, aka @buildscientist, EJ Ciramella, aka @eciramella, Sascha Bates, aka @sascha_d, and Seth Thomas, aka @cheeseplus plus another installment of #DevOpsDearAbby!

Or, download Episode 29, or any of our previous shows!

Show Links/Notes

DevOps Dear Abby

@zsepi asks “Despite having worked maintenance years on legacy codebases at BigCo, I don’t see why people keep picking on ‘enterprise developers’; shouldn’t we approach code with the assumption that everyone did their best given the circumstances (culture, skills, deadlines, etc.)?“

@StevenMurawski asks via email:

Why are ops guys in primarily Windows environments looked down upon (or feel looked down upon) in the DevOps community? Very often references will be “oh, and on Windows” like the ops guys running Windows wouldn’t be expected to be as professional as their compatriots on the *nix side of things. How can a primarily Windows ops guy fit in to this DevOps community?

Join Us!

What’s your design and testing process for your organization’s build/release engineering tools?

Do you use active configuration management or the “baked AMI” approach?

Join the discussion!

Episodes / Panels — Comments Off
10
Oct 13

Because You Watched DevOps, You Might Enjoy Netflix

It’s hard to have a conversation or hear a presentation these days about DevOps without hearing Netflix’s name being uttered: they’re a poster-child not only for employing DevOps principles and techniques, but for successfully moving their entire application to Amazon’s Web Services public cloud. But how did they achieve this? And what cultural and technological struggles did they have while reshaping themselves from a company that mails out DVDs to a company that slings bits and produces Emmy-award winning content. Join us for a chat with members of Netflix’s Engineering Tools and Playback Reliability teams; we know it’s a conversation you won’t want to miss… after all:

Because You Watched DevOps, You Might Enjoy Netflix

Join J. Paul Reed, aka @SoberBuildEng, Youssuf El-Kalay, aka @buildscientist, EJ Ciramella, aka @eciramella, Sascha Bates, aka @sascha_d, and Seth Thomas, aka @cheeseplus plus the last couple of weeks in News & Views!

Or, download Episode 28, or any of our previous shows!

Show Links/Notes

Join Us!

What cultural struggles does your organization deal with?

Would “context, not control” work in your company?

Join the discussion!