Stories
Slash Boxes
Comments

SoylentNews is people

Netflix's Engineering Model: Write Code Really Fast

posted by n1 on Monday November 10 2014, @10:49PM   Printer-friendly
from the who-cares-about-quality dept.

microtodd writes:

I thought this was an interesting presentation by Adrian Cockcroft at Netflix.

I know a lot of people think "DevOps" is a dirty word but the way Adrian describes how it works at Netflix is really interesting. This seems to be the embodiment of the "get out of the engineer's way" approach. And its more of that "speed of iteration wins in the marketplace" mentality I've started to see in the past few years. I liked the OODA loop callout in the slides, too....seems like Adrian might actually know who John Boyd is.

What do my fellow soylenters think? Better to give a developer ownership of the entire lifecycle? Or better to have defined checkpoints and stakeholders to ensure quality and defect prevention/identification?

 
This discussion has been archived. No new comments can be posted.
Netflix's Engineering Model: Write Code Really Fast | Log In/Create an Account | Top | 39 comments | Search Discussion
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

  • (Score: 2) by c0lo on Tuesday November 11 2014, @11:01PM

    by c0lo (156) Subscriber Badge on Tuesday November 11 2014, @11:01PM (#115000) Journal

    Its a parody word, like "agile", those words don't really mean anything, anymore.

    With all respect, I disagree in regrads with "no meaning" for devops (I won't comment on "agile").

    I find devops a useful term to express a reality in which the applications are adjusted/enhanced/modified, tested, deployed in very short cycles, which involves not only developers by sys /network/database admins. It happens as an everyday mode of life at my current workplace: a research joint, where the researchers need/use application custom developed in-house by a small dev team (about 6) while the rest of the "ops" part is made from about 15 others (network, storage, HPC, phones and A/V equipment, digitally integrated lab equipment, etc).
    It's like building a plane around the travellers while in flight.

    --
    https://www.youtube.com/watch?v=aoFiw2jMy-0 https://soylentnews.org/~MichaelDavidCrawford
    Starting Score:    1  point
    Karma-Bonus Modifier   +1  
    Total Score:   2  

  • (Score: 2) by VLM on Wednesday November 12 2014, @12:22PM

    by VLM (445) on Wednesday November 12 2014, @12:22PM (#115146)

    "very short cycles"

    I don't think we're necessarily disagreeing here. "devops" is at least a paragraph, if not entire books, that summarize to "shorten/speedup the cycle".