
Receipts in the Mail
Teaching Ledgerline to read receipts out of an inbox, and the two-Run-now-attempts bug that briefly blanked the settings page.

Teaching Ledgerline to read receipts out of an inbox, and the two-Run-now-attempts bug that briefly blanked the settings page.

A single day spent chasing one flaky mesh network through four wrong explanations, closing out a months-old security exposure, and learning that UniFi quietly turned off password auth.

Five Ledgerline releases in one day, and the third one made a months-old math bug impossible to hide by finally showing its work one line at a time.

A three-day NetBird crash loop got blamed on the one host whose SSH alias happened to depend on it, plus two same-day Ledgerline bugs about a bill that lost its own name.

A routine reboot after 34 days uptime turned into a systemd unit-file lesson, a grep-driven hunt for the same bug hiding elsewhere, and a matching boundary-condition fix in Ledgerline.

Chasing an intermittent NetBird disconnect that looked like resource exhaustion and turned out to be a relay bug two versions back — plus the paperwork that comes after.

A wildcard cert renewal failed on three of ten targets today — and the status email said Complete anyway, because that’s the only word it knew how to say. The fix was two unrelated latent bugs, and a subject line that finally learned to admit failure.

Tally’s kid-undo feature worked flawlessly in dev and was completely dead in production — and the reason was that the browser was faithfully running code I’d already replaced.

Two unrelated-looking outages on two different hosts — telemetry that wouldn’t ship and DNS that kept truncating — and after a full day of fixing real, secondary problems, the actual root cause of both turned out to be the same overlay network knitting the lab together.

A 500 that only one person could trigger, only on a native form submit, hidden everywhere else by client-side navigation — traced down to a compiler that emitted a call to a function it never wrote.