For years I’ve kept notes — Notion pages, scattered markdown files, the odd voice memo — and rarely done anything with them. The thinking was always that they weren’t polished enough, or complete enough, or interesting enough to share.
That’s a bad reason to not write.
The engineers and architects I’ve learned most from weren’t necessarily the ones with the best-formatted documentation. They were the ones willing to share half-formed thoughts, honest post-mortems, and opinions they’d revised. The value was in the thinking being legible, not perfect.
So this is me making the thinking legible.
What I’ll write about
Mostly things I’m working through at work:
- Building and operating distributed systems in Java — the boring details that matter
- Telecoms and network automation, particularly the gap between vendor promises and operational reality
- Cloud architecture on AWS, and increasingly how AI fits into infrastructure work
- Occasionally, the non-technical side of being a consultant: communication, estimation, trust
What this is not
It’s not a newsletter. It’s not a content strategy. It’s closer to a working notebook that happens to be public — which means some posts will be rough, some will be short, and some will be wrong. I’ll update things when I change my mind.
If something here is useful to you, that’s a bonus.