> these on call rotations aren't skills.
Troubleshooting live production issues is a skill.
Triaging incidents to prioritize actions to minimize user harm is a skill.
Assessing tradeoffs of mitigation strategies is a skill.
The very tangible scenario of being woken up in the middle of the night builds empathy with your devops / SRE organization (which can manifest itself in designing more resilient systems, engaging in less risky behavior, improving documentation for the next oncaller, etc).
Oncall isn't for everyone, and it's certainly not worthwhile if you don't take away any lessons from it. But devs are ultimately the closest ones to their code, and they should take advantage of the opportunity to understand how it behaves in production.
> Ask yourself.. what's next? What are you looking to do after 25 years of being on call? Will you still enjoy it?
I've had bad weeks of oncall as well as quiet weeks. If it ever gets to a point where bad weeks are much more frequent, and nobody's doing anything about it, then yeah, I won't want to do it anymore. But as long as it's still providing value beyond humans providing blood / sweat / tears, and as long as we're actually trying to make things better, I don't mind holding a pager a few weeks a year.