Two hundred pieces in
What writing in public taught me about engineering, what I was most wrong about, and why the archive is the point.
tech, developers, and the code underneath
59 pieces tagged craft,
from March 7, 2025 to August 3, 2026.
What writing in public taught me about engineering, what I was most wrong about, and why the archive is the point.
The workflows that survived contact with real work, the ones that did not, and what the whole thing actually changed.
Every line you remove is one that cannot break, cannot be misread, and does not need to be maintained.
A number, agreed in advance, that fails the build. The only mechanism that has ever kept a system fast.
A checklist for assessing an unfamiliar codebase quickly — for a job, a due diligence, or a project you inherited.
A file that takes ten minutes per release and answers most of the questions your users would otherwise ask you.
State an invariant, let the machine find the counterexample. A twenty-year-old technique that fits this moment exactly.
Most onboarding docs are written by people who already know. Here is what a new engineer needs on day one, in order.
Not a survey of vaults. The specific practices that actually reduce risk, in order of what to do first.
Most review comments are noise or nitpicks. A small taxonomy of the ones that are worth writing.
It has no type system, no tests, no review, and it causes a disproportionate share of outages.
The bug that happens once a week and never in staging. A systematic approach to the class of problem everyone handles badly.