"OpsDev": it's time to put the "ops" in "dev"Charity Majors
schedule 2 months agoSold Out!
For years the cornerstone of the "DevOps" movement has been lots of people urging sysadmins and operations engineers to get better at writing code. "You can't be a real devops engineer unless you write software and tests!", they say. Well, they were right, and message has been received. Writing software is now a part of every engineering interview.
But ... is that where it stops? What about all the developers who barely know how to log in and debug their own software, or who have no idea what happens to their code after they deploy it? They need DevOps too ... or rather, they need "OpsDev". They need the critical skills that have long been associated with operations and systems engineering: reproducing complex bugs, optimizing queries, designing and building resilient infrastructure, deploying their own services, instrumenting them for debuggability, scaling and owning and monitoring high quality services.
This is not just a fuzzy culture talk, it's a very practical talk filled with real tips and stories from teams that have undergone the hard switch. Lots of software engineers dread this transition, but 1) you aren't really going to have a choice before long, since dedicated ops teams to clean up messes are fading away, and 2) this is a better world and you should want it! Having solid ops skills makes you a superhero. Empathy and shared crossfunctional skill sets create a better world for all of us.