Which is worse when working on production databases? Being drunk or tired? (opens in new tab)

However, I think one under-recognized problem is that there is a complacency that comes with being tired. And when I look at the really big incidence response disasters, that has always been a major factor.

And yet we celebrate people who put us at risk....

As a result drunk individuals usually are facing narrow technical problems where thinking is required, and judgments already made, while tired people are facing the whole situation.

On call engineer wakes up to an alert. Realizes there is a major problem developing that he or she is underqualified to handle. Escalates the call.

Eventually this gets escalated to the top subject matter expert in the company. He's not on call, has been out partying, and is drunk.

Where does this become unacceptable? I am certainly not saying people should show up to work drunk, but unless you say anyone in the escallation chain may never be drunk, it is going to happen.