Well... For me (sysadmin) DevOps is a thing in theory, another in practice. The overall results of this dichotomy are tragic, they led to harmful things like do

Well... For me (sysadmin) DevOps is a thing in theory, another in practice. The overall results of this dichotomy are tragic, they led to harmful things like doker, k*s and so on down to GNU/Linux desktops crap like snap/flatpack/appimage. Yes that's not sound much "DevOps" but that's the product "DevOps" in practice have created IRL. That's because the Ops part is essentially reduced as a kind of low level mechanical works "please guys just give up the most bare bone system, we will do all the rest" and the Dev part surge to "if it works on my craptop [but well docked on a large set of display] than it works in production, we need to be quick, just grab something from DockerHub, the Nexus, ... and in few hours we will made a new successful Silicon Valley Fever project". It's natural evolution, that could be labeled "cloud APIs", part of the Serverless "model", is even harmful. The real issue though are not these model but the modern software stack and the story date back decades, when Unix was born their author think they can separate the "system" (bootloader, kernel, basic userland) and "the rest", allowing cheap end-user programming via scripts assembling system functions through IPCs. They quickly discover this approach is fast but fairly limited and they added GUIs violating their own principles since their GUIs can't be assembled with scripts and have only cut&paste/D&D as sole IPCs. A more broad and precise analysis can be found in the Unix Haters Handbook, but as Unix get ground quickly so "modern" GUIs do the same and we quickly evolve from "internet as a network of flexible, user programmable desktops" to "internet as a network of hosts serving some limited desktop to a "internet as a network of hosts who own anything and some modern dumb terminals named endpoints" and that's the present with desktops that are very complex browsers bootloaders, witch are themselves very complex virtual machines, and "the real intelligence" in code is now some third party services offering APIs modern Dev(s) use to assemble their very complex and unmaintainable script named webapps. DevOps was an intermediary step of this hyper succinct mess. We need to came back to an-OS-is-a-single-application where anything is integrated so things like reading emails meaning a network mount of a remote share, provided by the system, and a stat/read of few files in there, the messages, sending it is just mounting the receiver mailserver share creating a new file there if allowed, similarly reading a website is just the same and so on, oh, it's the Plan 9 model. Oh, such systems are like Smalltalk workstations or LispM where anything is a function that can be called, modified, combined with any other with few lines of code. This model is hard to evolve system side because there are MANY interdependencies to be taken into account, BUT allow to makes modern hyper-big projects a simple and manageable codebases where there is no need of CI/CD because updating is just patching in a version control system, so is rollback and third party services offers just what they want without specific APIs to support. I know described like that in my limited English is a bit confuse, but if you try reasoning "being outside" you'll see the big picture easier.