Tag: servicing
-
TGIF?
This was some years back, but I can still feel the visceral disbelief that it was fine to put the issue aside when they were ready to stop working for the day, but it could not be more urgent to wake us up at 2 AM.
-
It’s Business Hours Somewhere
Seriously though, it does suck to have to be the one waking other people up at their 3 AM.
-
Failover Fail
So you’ve got the high-tech velociraptor enclosure, but those velociraptors are pretty crafty and keep finding weaknesses. So you build a fence around the enclosure – no expense spared – and the fence immediately falls down, knocking out an enclosure wall, and now there are velociraptors in the kitchen.
-
Niche Issues
Hopefully it’s not too much of a commentary on my ability to call the right person. I at least feel a bit better when it is not something obvious and other people also don’t have any idea what’s going on.
-
As Soon As I Close My Eyes
I often find myself having trouble sleeping while on-call expecting that alert to happen at any moment. How annoying to be the one responsible for messing up my own sleep when nothing happens.
-
How Sure Are You?
It’s even better when the conflict is impossible: “So you detected the issue 3 hours before it started?”
-
In the Dark of the Night
Thankfully this particular scenario happened some time ago and it’s less common now for another team to gleefully ignore the severity classifications.
-
Documented Pattern
How often are we supposed to read that stuff again after we implemented everything?
-
But It’s Too Difficult!
The real argument was somewhat more nuanced than this.
-
Learning Opportunity
It’s nice when you can make a low-stakes mistake rather than a really catastrophic data-loss type of mistake.