> They are similar skill sets but the domains are different. Exactly. They're specializations, like heart surgeon vs. orthopedic surgeon. > I have been at th

> They are similar skill sets but the domains are different. Exactly. They're specializations, like heart surgeon vs. orthopedic surgeon. > I have been at this for 25+ years and I remember the days of silos. 32 years for me. Silos evolved out of the wild west of the 90's and early 2000's. Which evolved out of the strict controls of early computers run by a cult of Operators where the devs couldn't even access the machine directly. It's a cycle, where management tries to remove people, only to have to put them back later. I've seen it over and over. > I remember developers passing off code to QA and it coming back days later with bugs. It is literally QA's job to find bugs that developers missed. > In SaaS, that is production and should be the developers SaaS or not doesn't have anything to do with it. > As Ops, my goal is to make that as easy for possible for developers. As a developer, my goal is to deliver high quality code that meets the requirements for performance, stability, monitoring, security, and functionality. > They took developers and made them own everything from code to deployment to VMs. The developers had so many pieces to understand that the only guarantee was failure. I've never seen DevOps done any other way. Hence my original comment.