I woke up at 1:27 PM today.
I checked my phone. I had missed a 1:00 PM meeting with the CIO.
My Slack status had been set to "Away" for nine hours.
He sent a message: "We're waiting on the call. Where are you?"
I didn't panic. I didn't apologize.
I rubbed the sleep out of my eyes and typed:
"Sorry! I was up until 4:30 AM manually re-indexing the SQL fragmentations. The automated script failed and I didn't want to risk data corruption during business hours."
(I was actually up until 4:30 AM watching a 4-hour YouTube documentary about airplanes).
His reply came in 10 seconds:
"Wow. Thank you for catching that. Please, get some rest. We can reschedule."
The Lesson: Management doesn't know what we do. If you use words like "fragmentation" and "corruption," they won't fire you. They’ll thank you for your sacrifice.
Incompetence looks exactly like martyrdom if your vocabulary is technical enough.
I’m going back to bed
I checked my phone. I had missed a 1:00 PM meeting with the CIO.
My Slack status had been set to "Away" for nine hours.
He sent a message: "We're waiting on the call. Where are you?"
I didn't panic. I didn't apologize.
I rubbed the sleep out of my eyes and typed:
"Sorry! I was up until 4:30 AM manually re-indexing the SQL fragmentations. The automated script failed and I didn't want to risk data corruption during business hours."
(I was actually up until 4:30 AM watching a 4-hour YouTube documentary about airplanes).
His reply came in 10 seconds:
"Wow. Thank you for catching that. Please, get some rest. We can reschedule."
The Lesson: Management doesn't know what we do. If you use words like "fragmentation" and "corruption," they won't fire you. They’ll thank you for your sacrifice.
Incompetence looks exactly like martyrdom if your vocabulary is technical enough.
I’m going back to bed