I don't think the parent was implying you're never on call for your code, just only on call during working hours. One of the challenges for larger companies in

I don't think the parent was implying you're never on call for your code, just only on call during working hours. One of the challenges for larger companies in trying to make teams on-call 24/7 is that your most senior engineers often have enough money that they don't have to take on-call. Some variation of the following conversation happens in Big Tech more than most people seem to anticipate: "hey, so I have 7 mil in the bank, a house, and kids; so I'm not taking on-call anymore" "I understand on-call is a burden, but the practice is a big part of how we maintain operational excellence" "Alright, I quit" "Woah woah woah, uh, ok, what about we work on transitioning you out of on call over the next 6 months?" "Nah, I'm done" "This is going to be really disruptive to the team!" "Yeah man it sucks, I really feel for you" My understanding is a few famous outages at large cloud providers are a direct result of management not anticipating these conversations and assuming 24/7 on-call from a single geographically centered team of high powered engineers was sustainable.