You've decided your definition, as many have. DevOps as written is not what you're saying; this has been mentioned at least 20 times in this thread. Sysadmins

You've decided your definition, as many have. DevOps as written is not what you're saying; this has been mentioned at least 20 times in this thread. Sysadmins of yore were developers, they used perl and C and eventually ruby. Then there was a glut of sysadmins who couldn't code, then people acquired collective amnesia that sysadmins ever coded and invented a new term. The issue was that the term that they decided to use for this new breed of developer operations folk was the same word that was used for a methodology of breaking down siloes (having developers and operations as distinct entities but working together)[0] and the same word that was being used to describe sysadmins adopting Agile[1]. The annoying thing about the passage of time is that you look back and see only what has changed and may conclude that those changes are a result of paradigm shifts: you could be right, but sysadmins were using proto versions of common paradigms now: version control integrations used to be bad and fragmented, but it was ops pushing VCS; infrastructure as code via cfengine; cluster management with clustered ssh clients (cssh). I was there, I saw this. It's hard to differentiate between the slow march of progress of operations tooling (rebranded as devops tooling) and the fact that it might not actually be linked to devops as a methodology. [0]: https://www.youtube.com/watch?v=LdOe18KhtT4 https://www.youtube.com/watch?v=LdOe18KhtT4 [1]: https://www.knowledgehut.com/blog/devops/history-of-devops# https://www.knowledgehut.com/blog/devops/history-of-devops#