Over the course of a 20+ year career, I did everything soup-to-nuts as a way to build broad experience and skills. So that included understanding how to build o

Over the course of a 20+ year career, I did everything soup-to-nuts as a way to build broad experience and skills. So that included understanding how to build out and secure infrastructure, build automation for deployment, rollback, etc, in addition to my main expertise in building software. I think it's commendable for developers to do this because it helps them anticipate and understand how the software will actually be operated. But what I found was that few employers really wanted this or were willing to pay for this added expertise. In fact many seem threatened by it, as they wanted to keep roles siloed. They didn't want to encourage cross-pollination of ideas or improvement. Maybe that sounds like sour grapes on my part, but that's what I observed. I'd say too that they ones who were keen to see developers add these skills did so because they wanted to cut the labor costs of people who were focused on operations - so now as a dev you were getting paid for one job but expected to do two.