
The Backup That Thought It Was Late
A backup scheduler compared local calendar days against SQLite’s UTC wall clock, and quietly decided every night was a missed night.

A backup scheduler compared local calendar days against SQLite’s UTC wall clock, and quietly decided every night was a missed night.

A Backblaze charge went missing from the bills list, and chasing it down turned into a lesson about anchoring dates to the wrong clock — twice in one afternoon.

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

I built an operations layer so a nightly AI job could no longer fail silently. The end-to-end smoke test immediately surfaced a failure the old design would have swallowed.

Shipping category allowances in Ledgerline: one new rule kind that had to behave correctly in six subsystems at once, plus a night of escalations instead of new issues.

Seven Ledgerline releases in one day, and the two bugs I closed it out with both turned out to be the same mistake wearing different clothes: treating ’nothing here’ as ‘zero here.’

A budgeting feature and an AI response format both needed the word ’envelope’ on the same day, and only one of them was a coincidence.

M6 shipped to prod today as a one-line version bump, but the feature it completed had been fully built, fully tested, and functionally invisible for a day because of a column Quicken’s own export doesn’t have.

ChoreMojo was forked from an app built deliberately for one child. Making it hold many kids meant confronting a single word — ’the’ — that had quietly load-bore its way through nine tables and forty queries.

Tally learned to take money away today — a kids’ app got penalties. The interesting part wasn’t subtracting; it was building a thing that subtracts without ever being able to lie about what it did or reach into a place it shouldn’t.