“Why don’t you engineer a big catastrophe, and then you fix it all and look like a hero?”
I was talking to someone about how amazingly ‘boring’ and uneventful my recent go-live was (just the way I like it!).
We spent time preparing, reviewing and re-reviewing our cutover list, checking environments, doing dry-runs of a major platform upgrade on a sandbox, checking timing and performance… almost anything we could have thought of.
Deployment started at 0400 BST (client wanted to go-live before US came online) and proceeded smoothly, and although we had a few hiccups, we were able to get back online ahead of schedule.
No, I don’t want manufactured ‘catastrophes’ so that we can look good.
I spend my working life trying to iron out kinks in projects so that we achieve our outcome in a quiet, competent manner.
You don’t hear much when a good system administrator is at work.
That’s because they keep the system running well.
No big servers crashes.
Databases backed up diligently so if things went wrong, they were restored quickly and quietly..
Users hummed nicely in their work space.
I think it’s better that way.
Quietly competent is a really nice way to go about our business.