> By spreading the load across the dev team I can automatically get a high bus factor and 24/7 hour on-call rotation. This assertion supports what vidarh wrote

> By spreading the load across the dev team I can automatically get a high bus factor and 24/7 hour on-call rotation. This assertion supports what vidarh wrote. What you wrote has nothing to do with DevOps or software or engineering - what you are really saying is that you are saving money by coercing your developers into working two jobs at the same time. I have been in this position as a developer at a company where we had on-call rotations. This is a false economy and a quick way to increase stress, alienate employees, and increase turnover. Infrastructure tasks get neglected and are performed poorly because those tasks are now just necessary distractions to the main workload of feature development, to be gotten over with as quickly as possible. A lot of things get overlooked because no one "owns" areas like backups and disaster recovery.