There's a salutary effect on developer conscientiousness to put them on call for problems with their own code on production. If a missing nil check means that y

There's a salutary effect on developer conscientiousness to put them on call for problems with their own code on production. If a missing nil check means that you get dragged out of bed at peak REM sleep, you check for missing nils harder. You test more. You design your whole project around the requirement of getting uninterrupted sleep. For years I was in this position for a trading company that had pre-market downloads at 4am my time. Bad data and my own bad code woke me up a lot ... which contributed a lot to making that code wake-me-up proof for further years. Of course you should get paid for that time, and there's a diminishing return to such character building exercises. But eating your own dog food is worthwhile particularly in the middle of the night.