Or: the older you get, the stronger the imperative is to automate fault handling in your environment.
Last night I got a text at 2:36am. Being the sysadminly on-call type that I am, I leaped out of bed still half asleep. I keep my phones on a cell phone stand that's really loud when something is vibrating on it, so I've been trained to get up when that racket starts. This was my phone going buzz, which meant I missed the work-phone going buzz (I have two for a reason).
It was when the phone was in my hand that I remembered that I'm not on any on-call schedule right now.
R u male or female?
From a west-coast area code.
An interesting question as it happens, but not my infrastructure crying for parental guidance. Or worse, the actual on-call people being over their heads and needing my help. Nope, just some lost soul hoping for love.
Shut off phone, went back to bed.
Whereupon I stayed awake another two hours.
Had this been an actual emergency, work would have been understanding of me coming in late after a late-night call-out. Like that time I dealt with a major infrastructure failure on 3.5 hours of sleep. They're nice that way.
Sleep disruption like that is getting more common as I get older. I give thanks that my infrastructure doesn't usually cry mommy in the wee hours, and if there is crying it's more likely to happen in the evenings than at 3am. That evening call-out may have me working until 3am, but that's better than getting 2 hours of sleep and getting woken up.