All Posts
Terminal Dispatches
Green-on-dark brutalist for developers. No frills, all function.
postmortem
Postmortem: The 41-Minute Retry Storm
A 90-second provider blip turned into 41 minutes of our own errors. Timeline, the commands we ran, the three-line diff, and why a retry loop without jitter is a synchronized weapon.
dependencies
Why We Pinned Tidewrangle at 4.2.1
A minor release changed how a date library handled timezones, and our invoices shifted by a day. What a caret range actually allows, and the rules we use to pin on purpose.
debugging
Reading a Crash the Way You Read a Core Dump
A core dump is a frozen process, and reading one is a short checklist: the signal, the faulting address, the frames. Here's that checklist applied to a crash you can reproduce in a minute.
build
Tuning a Build Cache Until It Stopped Lying
Our CI cache was fast and wrong about once a week. Keying it on file contents, not timestamps, fixed the wrong answers, and it fixed a good share of the slow ones too.
testing
Hunting a Test That Fails One Run in Fifty
A flaky test is a failure you can't replay. Pin the randomness behind a seed, sweep the seeds, and the one-in-fifty ghost becomes a number you can type into a terminal.
cron
The Nightly Export That Ran Twice
A cron job that took 70 minutes on an hourly schedule produced duplicate rows for three days before anyone noticed. The timeline, the fix, and a lock you can run yourself.