> A counter point is that being a professional software developer is more than shipping features, you have to ship something that is profitable in the long run, which requires you have a broader perspective than your desire for a narrow focus.
I think what's more common, particularly in mature companies, is that the responsibilities are getting split between those that manage the complexity of infrastructure and software developers. Software devs might dictate the infrastructure requirements in their own terms like systemA should have access to systemB, but they're not going to be setting up the Amazon security group.
> A counter point is that being a professional software developer is more than shipping features, you have to ship something that is profitable in the long run, which requires you have a broader perspective than your desire for a narrow focus.
I think what's more common, particularly in mature companies, is that the responsibilities are getting split between those that manage the complexity of infrastructure and software developers. Software devs might dictate the infrastructure requirements in their own terms like systemA should have access to systemB, but they're not going to be setting up the Amazon security group.