The O-Ring Theory of DevOps
I don&#x27;t know if this is O-Ring theory as much as a &quot;six sigma&quot; style process. The quality of each output depends on the quality of the inputs, and imperfections grow exponentially when things fall out of tolerances.<p>The whole point of DevOps is really to get your software developers to share in the pain that certain design &#x2F; development choices can cause. In the absence of some DevOps-like process, dev teams will naturally shovel all their tech debt on the operations team. Rather than build their software to handle multi-tenancy, they&#x27;ll just say &quot;Eh, deploy another VM with a different configuration&quot;. Not that that&#x27;s necessarily the wrong answer, but because it&#x27;s less work for them, they don&#x27;t take into account how hard it will be for the operations team to manage. If the dev team is responsible for both building the software, the tools used to manage the deployment, and responsibility for incident resolution, they&#x27;ll make decisions that are better for the company and its customers.<p>That&#x27;s my take, anyway.