What I do

Most of my work sits in three places, and so does most of what ends up here:

  • Infrastructure — standing up and keeping the environment that everything else runs on.
  • Tool development — writing the diagnostic or the automation when the vendor's version doesn't fit the problem.
  • Training and documentation — writing the runbook so the next person doesn't start from zero.

What's here

Two collections. Tools are things you can run — diagnostics, migration helpers, bulk utilities, each with the reasoning behind it. Write-ups are the longer accounts of work I've done: what the environment looked like, what the plan was, and where it went sideways.

Both get published because the version of these write-ups I wanted to find, when I was in the middle of the problem, usually didn't exist. Failures stay in. A migration guide that only lists the happy path isn't much use at 2am.

Get in touch

I'm glad to hear from other infrastructure and security people — about the tools here, work you're stuck on, or anything adjacent.


Everything here reflects my own experience and views, not those of any employer or client.