DevOps is a movement about the management of computer programmers. It basically says that Development (coding) and Operations (deployment and maintenance) should communicate more and better. Such workability allows for better error detection, swifter deployment of code, etc.
Interestingly, I’ve worked mainly in research environments where I’ve been in charge of both Development and Operations at the same time. I worked in a corporation with separate Dev and Ops for a few years – and I worked on the Ops side then.
I agree wholeheartedly with the insights this book shares. I like rapid, swift, and small deployments over heavy and charged deployments. That allows life to be better on the developers and the operations folk. I prefer to be able to roll-back a small change (that happens several times a day) instead of potentially disabling a system with a large change. That’s how I maintain my code personally, so I have no problem with asking an organization to do the same.
I’m continuing to read about the movement towards a combined DevOps role. Apparently, this group puts out annual reports and has been pushing this out since 2014. It is viewed as a successor to Agile Management of projects. I appreciate their voice and their contribution for the management of computer programmers.