Writing
Essays on building and operating production systems alone: what documentation claims, what technical debt costs, and what measurement says afterwards.
-
18 August 2026
I Built the Rollback. I Have Not Given It Permission to Act.
The rollback is designed and staged and holds no permission to act, on purpose. What a system is allowed to decide, and how that permission gets earned.
-
13 August 2026
Confidence Is a Claim. Almost Nobody Grades It.
A confidence value is a falsifiable statement about the future, and almost nothing in a deployment pipeline ever goes back to check it. Two of my modules failed that check.
-
10 August 2026
Documentation Is a Claim. Code Is Evidence.
I audited every technical claim in my own documentation against the code it described. Six came back wrong, on the cleanest codebase I had available.
-
5 July 2026
Four Roles in One Head
Two months of architecture before a line of code, then a weekly loop of measure, plan, build, ship. What building a product alone actually asks of you.
-
10 March 2026
Technical Debt: Quiet While It Accumulates, Sudden When It Arrives
The expensive part of technical debt is not the old code. It is the upgrade you can no longer take, the dependency past its end of life, and the security patch nobody applied.
-
8 March 2026
Communication Is Not a Soft Skill
Technical competence loses its value in the absence of communication. Where software delivery breaks, and why the repair is a habit rather than a process.