As far back as 2000, our “ops” person wrote Perl scripts using the Win32 module to automate tasks on our 20 windows job servers. Even in the mid 90s when I wor

As far back as 2000, our “ops” person wrote Perl scripts using the Win32 module to automate tasks on our 20 windows job servers. Even in the mid 90s when I worked on backend mainframe systems for lotteries, everything except physically changing out tapes and malfunction hardware was automated. There has been an API to manage networked servers since networking existed. The value add of DevOps was suppose to be developers and operations working together. When I develop something. I always do it with a mindset of how will it be deployed, scaled, monitored, etc If “DevOps” is a role instead of an institutional behavior, you get none of those benefits. And yes I know “Devops” [sic]. My day job is consulting companies on how to bring modern development and cloud operations, networking, CI/CD, monitoring, aggregate logging, etc together. I work up and down the stack from an empty AWS account to back end development and if you put a big enough gun to my head, I’ll deal a little with the clusterfuck of front end development