Writing
Notes on the parts of the work that took a second attempt. Most of these started as a comment in a codebase, at the point where the decision was actually made.
Five years of notes in one company’s file format is a bet on that company. The test isn’t whether the app is good, it’s what you keep when it stops existing.
The gap between a good engineer and a great one is rarely who can write the code. It’s who noticed the detail was there to be got right.
The most reliable thing I do with a coding agent: write the types by hand, then let it write the code that satisfies them. The type is the spec it can’t argue with.
The best-practice repos shipping for coding agents aren’t new knowledge. They’re the first time anyone had a reason to write the old knowledge down.
next/font already ships a fallback face re-scaled onto your webfont’s metrics. Naming your own system stack replaces it, and takes the shift-free swap with it.
A UI system with one axis. Four surfaces, three nested radii, and a border token set to transparent so the shortcut isn’t there to take.