That hasn't been my experience from the folks that actually grasp the concepts. As an ops person myself, I spend the bulk of my time writing code. It just isn

That hasn't been my experience from the folks that actually grasp the concepts. As an ops person myself, I spend the bulk of my time writing code. It just isn't product code. It is code for an internal customer, the devs. Sometimes I do small commits to the product codebase, but not often. I think you see devs make this comment cause they think they are doing "ops work" instead seeing it as consuming the ops team's work. It isn't about everyone doing equal code commits. It is about speeding up things across the whole business. Every ops person you hire is money you don't have for a dev. It is more efficient to enable the devs than it is to hire ops people to do a small portion for their job. Same goes for QA. The groups that have really got the message are including QA teams that handle much of the testing via automation. A good QA team writes code. There is plenty of development going around. It just might not be on product code itself.