About
I’m Curt. I work in IT — systems administration, networking, self-hosting, and the operational documentation that keeps it all from falling apart.
Most of my day-to-day is about making infrastructure easier to fix, easier to hand off, and harder to break by accident. Reverse proxies, DNS, backup verification, monitoring, and the small automations that keep routine changes from going sideways.
I like systems that still make sense when you’re troubleshooting them at 2am. That usually means simpler naming, better rollback plans, and notes that are actually useful during the incident — not just after.
I’m opinionated about documentation. If it can’t help someone make the next correct decision during a change window, it’s too vague. I write runbooks while the fix is still fresh and keep them short enough to actually get read.
This site is a static export served from my own infrastructure. The blog and knowledge base are markdown files in a git repo.
How I work
When something breaks, I follow contain, compare, verify, document. When building, I’d rather have three simple things I understand than one clever thing I can’t debug. I write documentation as part of the work, not after it.