I'd prefer that as well, however I end up being the one woken up because your (the generic you) code has errors. If you're not willing to be on call I hope you're at least "willing" to be terminated if your code wakes someone up every day of their rotation (yeah, been there).
If you are not willing to work outside 9-5, if you are not willing to sacrifice your scarce free time, then you must produce perfect bugfree code. Is that?
I have to give it to the companies and to the whole devops/agile movement. They have truly convinced us that being oncall is the right thing somehow. And that non oncall engineers are a somewhat inferior race.
When the alternative is expecting someone else to give up their scarce free time, yeah, you'd better be producing perfect code or work somewhere that doesn't care about overnight outages.
Maybe it’s not about anting to write perfect code but a higher business unit that starts wildfires because a important and influential stakeholder from that one group of high paying customers complained loudly about something not working at 2am and next thing you know there’s a “planning for on call” meeting on your calendar
