DevOps is a failure
&gt; If you look at a DevOps engineer job description, it looks remarkably similar to a System Administrator role from 2013, but...<p>&gt; If DevOps was supposed to be about changing the overall culture, it can’t be seen as a successful movement. People on the operations side of the fence will...<p>As someone who was keenly watching this stuff back 15 years ago, parts of this article connect with my understanding, but the core problem I have is that this article itself is somehow bought into the mistake that led to the failure and so almost can&#x27;t see the failure for what it is: the entire point of DevOps was that &quot;operations&quot; isn&#x27;t a <i>job</i> or <i>role</i> anymore and has instead become a <i>task</i> that should be done by the developers.<p>Ergo, if you even still have operations people to comment on it--or certainly if you are somehow hiring dedicated &quot;DevOps&quot; people--you aren&#x27;t doing DevOps and have already failed. The way to do DevOps is to fire all of the Ops and then tell all of the Devs that they are now doing DevOps; you simply can&#x27;t have it both ways, as that&#x27;s just renaming the same two camps instead of merging them into a single unified group.