No.  Originally it was about operations and developers collaborating more closely, including cultural change (devs don&#x27;t throw things over the wall to ops, ops doesn&#x27;t hide prod from devs), increasing automation (applying development methodologies to operations), improving learning between the ops and dev teams, and such.<p>These days it&#x27;s sometimes used:<p>- to mean traditional ops<p>- to mean that devs do all of their own ops<p>- to mean that there&#x27;s a separate silo between the dev and ops silos that make tools<p>- to mean the original thing about collaboration and a shift on the ops side to be more programmatic.<p>Your explanation is a complete and total myth, though.  It&#x27;s just some garbage from a programmer who didn&#x27;t know what it meant and decided to be a huge jerk about it.