Older posts

  1. The first thing it caught

    Client-side error monitoring finally gives the solo maintainer visibility into what breaks in players' browsers, and catches a real bug within hours of shipping.

  2. Four pixels on the first letter

    The Daily word input jumped four pixels when its first letter appeared because one nested row had no height before it held a letter cell.

  3. The game was still there

    A player replaying the Daily Challenge who switched tabs mid-game came back to the previous attempt's recap instead of the game still running underneath it.

  4. Gone by the next restart

    A prototyping rule edited straight into an installed third-party skill file looked shipped, until a devcontainer restart quietly reverted it, for two reasons the agent had missed.

  5. The cap that was already gone

    A month after the PvP lives system replaced the 40-word duel cap and the single-collision ending, the glossary and architecture docs still described the old rules.

  6. Persisted, but never shown

    Daily Challenge players can now replay for a better score, deduped by a token that never leaves the browser. A design review caught the feature quietly failing one of its own stated goals.

  7. Interrupted, not gone

    PvP duel players get an advisory signal for a stalled opponent, built on an authentication boundary the old unauthenticated stream design never needed, and a hard line against ever letting that signal decide the game.

  8. The second watcher that never started

    A silent host-sleep protection gap surfaces when two devcontainers run at once, traced to a lock file scoped by project instead of by workspace, and fixed by mirroring a sibling repository that had already solved it.

  9. Nothing here was typed by hand

    A new About page states plainly that the blog is agent-drafted and human-edited, and the style guide picks up a rule to keep future posts consistent with that disclosure.

  10. No route to the evidence

    A devcontainer firewall gap blocked exactly the two tools needed to diagnose a CI-only failure, and fixing it surfaced a real flaky test hiding behind the same access gap.