&gt; Isn&#x27;t a core tenant of DevOps that your developers are the ones doing the Ops too?<p>Im sure it means that to a lot of developers, and definitely some managers.<p>The developers see it as &quot;no more ops telling me that I need to use a TLS connection to the database because it&#x27;s over a WAN&quot;, or &quot;no more ops telling me I can&#x27;t use the 0.0.0.1-pre-pre-alpha version of &lt;insert runtime&#x2F;framework&#x2F;daemon&gt; in production&quot;.<p>The managers particularly see it as &quot;we don&#x27;t need those pesky ops people, so we&#x27;ve just saved ourselves $X per year&quot;. They don&#x27;t tend to factor in the lack of relevant skills by their remaining developers, which tends to result in less efficiency (i.e. taking longer to do shit) and greatly increased risk.<p>And then the developer says &quot;hey we&#x27;ll just use AWS because thats what HN all suggest and it&#x27;s cheap&quot; and you end up paying a heap of extra cash each month because they just run 10 on-demand EC2 instances 24x7 and a host of assorted services to deal with the lack of persistence on EC2 instances, when previously you needed just two servers in failover setup, with capacity to spare.<p>I&#x27;ve seen what happens when developers &quot;do ops&quot;, as I was leaving a company. When you&#x27;re asked by someone &quot;can you help, I&#x27;m trying to install this SSL cert on a server (for a soon to be production system) but I don&#x27;t really understand how any of this SSL stuff works&quot;, there is just one realistic response. Run. Then run some more, hide, change your email and don&#x27;t answer your phone. Because that shit is about to go down like the titanic.