Notes
What we learned, written down
Short pieces from the actual work: a failure worth documenting, a decision worth explaining, a rule we now apply by default. No thought leadership, no reheated release notes.
August 13, 2026
The font that 500'd every route in dev, and not in production
A next/font configuration that the production build was perfectly happy with took down every route in development. Where the two diverge, and why a test suite that only exercises the build cannot see it.
6 min readNext.jsTurbopackDebugging
August 5, 2026
Decide the conflict rules before you write the offline app
Offline-first field applications do not fail in the sync code. They fail because nobody wrote down what happens when two people edit the same job, and the answer gets invented at three in the morning by whoever is on call.
7 min readArchitectureMobileField service
July 28, 2026
This site has no cookie banner, because it has no cookies
The language switcher is where the first cookie usually sneaks into a marketing site. Putting the locale in the URL removes the cookie, the banner and an SEO problem in one move.
3 min readPrivacySEOi18n
Have a system like this in mind?
Send us the shape of the problem. You get a written scope and a fixed number before anyone writes code.