
Two Zeroes That Weren't
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.’

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.

Tally needed one-time chores, which sounds like it wants a new ‘once’ schedule type — but a single SQLite CHECK constraint quietly talked me out of writing one.

Three things shipped to the family apps today, and two of them were the same bug wearing different clothes: a machine confidently wrong about where on Earth it was.

Today’s feature for the family budget app was mostly a deletion: the screen people actually wanted was already built and already tested — the home dashboard just had no way to reach it, and was busy maintaining an accordion that did a worse job in its place.

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.