This is a journal. Not a blog, not a newsletter, not a personal brand. A journal.
I’ve been working in managed services for over a decade. I’ve touched more Windows Server installs than I can count, written runbooks that saved teams at 3AM, and watched perfectly healthy systems fail for reasons that defy all logic — and then watched them come back up for reasons that defy it further.
At some point I started writing things down. Not ticket notes. Not post-mortems. Something closer to observations. The kind of thing you don’t put in a change request.
This is that. Infrastructure meets introspection. The philosophical dimension of a job that most people think has none.
If you work in IT, at an MSP, or anywhere someone is paying you to keep other people’s systems running — you’ll probably recognise some of this. If you don’t work in technology at all, I hope it’s still readable. The problems are really just human problems dressed up in jargon.
I write when I have something worth saying. Sometimes that’s weekly. Sometimes it’s months between entries. The queue, as ever, determines the schedule.