I run a small homelab and a handful of side projects, and I write down what breaks. Most posts here start the same way. Something behaved badly, the obvious explanation was wrong, and the measurement said something else.
Mostly I care whether a system stays legible. If I can’t explain it six months from now, I’ll mis-operate it. So I care about clear names, honest defaults, dashboards that show state instead of edges, and docs that get corrected instead of re-derived.
Rules I hold myself to here. Every number traces to a file, a commit, or a command I ran. If I got it wrong the first time, the post says so. Length isn’t credibility.
Work history, in two forms. resume.dustinholden.com is the engineering one — Python, Django, and the platforms underneath. cv.dustinholden.com is the leadership one — the same career read as strategy, budget, and org. Code is on GitHub, and email reaches me at dustin.holden@gmail.com.
This site is plain Astro, one stylesheet, no analytics, no tracking, no newsletter popup. There’s an RSS feed and nothing else to sign up for.