This is a good assessment of many of the angles of an on-call rotation in a technology team. I agree with the conclusions, and also agree with the premise that all team members for a service or set of services should be in the on-call rotation.

Teams where the people creating the software help support the software achieve better quality through aligned incentives and increased awareness.

I like that this article calls out the elephant in the room, that there is a general culture in many organizations that developers are “above” being on-call. That is crap and needs to be dispelled whenever it is brought up. If anything, I would highlight that there are a lot of developers are just aren’t all that great at being on-call. The skill argument should go the other way. Great operations engineers know how their software behaves, and they know how to push it and make it do what they want. Often the developers that wrote it have no clue. Also, the general stress and pressure of incidents is something that you need to have the stomach for.