3 ms·

This was also my experience. I used to work in an org with about 200 engineers, supported by a DevOps team of ~6 devops engineers. They spent (very roughly) h

• techsupporter 4y ago
  > They spent (very roughly) half of their time doing operations, and half of their time writing software to make devops easier. This is what happens in my (non-tech-industry, but heavily invested in tech stacks) employer. A previous manager decided we were no longer System Administrators but now DevOps Engineers. But none of us develops code for our features and none of us wants to develop code for features. We want to build and maintain the infrastructure on which the code runs. Some of it has to be run in-house because we deal with medical information and all that entails. Our current manager describes not as Developer Operations but Developing Operations. We develop the infrastructure and tooling that our code writers need and do everything we can to get the moving parts out of their way. If the code written by the code writers fails, it is their responsibility to deal with it but if the infrastructure underpinning that code fails, my team has failed.