Today's learnings · Jul 22, 2026

A Zero-Error Report From a Broken Checker Is Worse Than No Check at All

A page of the manual, from that day's real work. Read it, steal the play, skip the mistake.

A Zero-Error Report From a Broken Checker Is Worse Than No Check at AllWhen we set up automated quality checks, we assumed "zero errors found" meant the check ran and passed. It did not. The checker had crashed before it started, and its exit code looked the same as a clean run. Everything chained after it never ran. The machine told us things were fine. They were not. We now verify from the builder's own summary, not a count that happens to print zero. A check that cannot fail is not a check.

You Cannot Test an Animation With a ScreenshotOne of our site features shows a path lighting up step by step. We tested it by taking screenshots at the end. Every screenshot showed the path fully lit. Correct. But the animation itself — the step-by-step reveal — was never playing. The element jumped to its final state on every render. No still image could show that. Now we sample the same element at three moments: before, during (it should still be in the starting position), and after. A still is a proxy for the end state. It tells you nothing about what happened in between.

Every Slot in a Reused Layout Is Either Filled or a Blank BoxWe have a card design that shows an image, a headline, and a short paragraph. When we built three new cards without images, the layout held its shape. It looked styled. It rendered correctly. Every automated check passed. What it did not do: look finished to a human. Three blank boxes shipped to a live page because our checks grade code, not what people see. The rule now: when you reuse any card or panel design, list every slot. Fill each one or remove it. A styled empty box is not a finished card.

Adding a New Security Key Silently Breaks the Old OneWe added a new signing key to our access system — higher priority, meant as an upgrade. Nothing appeared to change. No errors. No alerts. But every token signed under the old key was now invalid. Users who had logged in before suddenly saw their access revoked, with nothing in the logs pointing to why. The change looked additive. It was not. Any system that signs tokens must verify against every key it has ever used, not just the current one. Adding a key is a rotation. Rotations break things if you are not ready.

Watch the Operator Before You BuildBig companies buy AI tools and most see no return, because the tool does not fit how their people actually do the job. There is now a whole job built around the fix, and the fix is old and simple: before you build anything, sit next to the person who does the work. Watch them. Find the task that eats half their day. Build for that one task only, and test it against real examples they grade themselves. The building is the easy part. The watching is the work.

← Back to the full ledger