Julia Evans looks at what DevOps means in practice:
I enjoyed reading this article about devops at Etsy. One of the really key things about this article is – there is no devops organization at Etsy. It’s about how developers and operations people work productively together! Also, it was a slow incremental migration towards different practices. They did not wake up one day and become devops. I think this is the first talk that used the term ‘devops’?
It’s also not about “everyone is a software developer” – one of the authors of this book, Katherine Daniels, is a senior operations engineer at Etsy at Etsy. I don’t know any of the details of her job, but my impression is that she has a lot of expertise in operations. It’s not like “make operations so easy that nobody has to an expert at it”. Of course you need people who know a ton about operations! Probably those people write software as part of their job?
One of the scariest realizations that I’m slowly coming to (other than “Information Technology is people!”) is the sheer number of overlapping dependencies in the tech world. A bit earlier in my career, I felt like I could be “a SQL Server guy” and focus on that while not caring too much about the outside world. It seems like saying that you want to be “just an X” has become more difficult at the margin, and DevOps is just one example of this: keeping an edge means going broader about more things while still trying to dig deeper in relevant areas. That’s a tough balancing act.