The missing link here is that "Ops" should no longer be the traditional imperative, reactive approach to systems design and maintenance. Ops in all three of th

The missing link here is that "Ops" should no longer be the traditional imperative, reactive approach to systems design and maintenance. Ops in all three of these becomes the modifier. This is why most practitioners today will tell you that DevOps/DevSecOps/SecOps are less individual titles and more a cultural way of thinking and operating and that the philosophy is executed by engineers of all types. It's important to remember the origins as well. Prior to DevOps, developers and operations teams were siloed in ways that hindered healthy growth in todays distributed systems and cloud environments. These "*Ops" terms were born of the necessity to impress upon people the importance of interoperability between traditionally isolated and independent departments. *Ops is the natural progression of Conway's Law into modern engineering organizations.