100% agree with this. I work on a service deployed in Azure processing PBs of data each day. We’re a team of about 8 engineers, and we have an on-call rotation.

100% agree with this. I work on a service deployed in Azure processing PBs of data each day. We’re a team of about 8 engineers, and we have an on-call rotation. As a result, we’re incentivized to reduce on call noise and have the system automate remediation as much as possible. Granted, our company does have centralized teams that build tooling. So that does seem to be a prerequisite to having full cycle developers. If you’re building in the cloud, I think there’s less need to be a SysAdmin these days (I used to be be one), and Azure makes it pretty easy to have automatic updates, firewall rules, etc. We rarely touch our hosting environment (Service Fabric on VMSS). The on-call sucks at times, but I’d never trade it for how fast we’re able to ship.