Absolutely this. I've worked on teams that do on-call rotations and teams that don't. What I typically find is that when you're on-call you work hard for your t

Absolutely this. I've worked on teams that do on-call rotations and teams that don't. What I typically find is that when you're on-call you work hard for your time off-work to be peaceful. Everything becomes infinitely better - code reviews, testing, deployments. When you do have an on-call issue that is beyond something simple and transient, it gets brought up in incident reviews for all engineering teams. This keeps everyone accountable and focuses team's efforts on patching anything that causes on-call pain. You really don't want to have to say anything in this meeting. And if you do on-call right and focus on quality, you're basically never doing anything during your rotation. On the flip side, when a team doesn't do on-call rotations the code quality suffers greatly.