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.

A third silent reboot ruins a perfectly good hardware theory, and a night of advisory triage turns out to be mostly about deciding what not to file.

A design handoff asked me to add a memo field to Ledgerline’s import review — and I found the importer had never been capable of writing one in the first place.

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.

A mis-typed IP address quietly turned one branch of the lab’s encrypted DNS into plaintext, and the only reason I found it was that I started shipping resolver logs the same day.

Seven Ledgerline releases shipped in one day — and the nightly drift monitor promptly filed a complaint about how fast I was moving.

D21 lands in Ledgerline — derived budget treatments with explainers and family allowance parenthood — ships to production the same day, and the nightly drift check catches its own deploy.

Retiring an abandoned container image across two fleets, teaching nginx to stop caching a container’s IP, and a research digest that mostly reported things fixing themselves.

The allowances UI ships and deploys the morning after the math did — including a table that shows a deliberately wrong balance, and a prod database with zero allowances in it.

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.