The DevOps Paradox: a Shift Away from Ops
<p>These days, we have such a hard time defining DevOps because the problem it initially solves is long gone.</p>
<p>For some recent companies, the problem never actually existed! They are doing everything correctly, but instead, the software engineering landscape has evolved so fast that the gap has been filled by tooling and cloud engineering.</p>
<p>We are far from the original day of DevOps and its culture shift aiming to break the silos between Dev and Ops.</p>
<h1>The Dev and Ops Silos</h1>
<p>Back in 2008, when Patrick Dubois first thought about DevOps, he was looking at the ineffective collaboration between development and operations in a context where project management had just moved from waterfall to Agile.</p>
<p>The operation teams at that time managed everything from networking, server, virtual machine, OS, and software updates. This effectively hid a lot of manual operations. Not everything was manual, but it was before Puppet, Chef, and Ansible — or even Terraform existed.</p>
<p><a href="https://betterprogramming.pub/the-devops-paradox-a-shift-away-from-ops-26b3615ed97e">Read More</a></p>