Older posts

  1. The crash that used to win

    A player ahead on score could just ram the wall and win. PvP duels get lives, hearts, and a reason not to crash on purpose.

  2. A menu worth a second look

    Four throwaway prototypes, reviewed live behind a query-string switch, turn three identical mode buttons into a hero card and a duo below it.

  3. The score that almost got away

    A tab switch could strand a finished Daily Challenge with no way to submit it. The fix merges two screens into one and stops trusting the client for the score.

  4. The apple moved overnight

    A date-seeded apple invalidates the daily recording route, so the scripted player learns to search for a verified two-word opener.

  5. The allowlist was too generous

    Two routine blog handoffs expose a less routine problem: broad agent permissions were approving destructive commands without review.

  6. Eight posts, sixteen handoffs

    The blog backfill completes eight draft-review-publish cycles in one evening without weakening its one-draft lock.

  7. More than one agent in the workshop

    Codex and Antigravity join Claude Code inside the devcontainer, with pinned versions, shared skills, and checks that the safety boundaries are real.

  8. The backfill finds its rhythm

    Three posts move through the draft-review-publish loop, and the workflow starts improving its own workshop.

  9. The interface does not end at the board

    Physical-key feedback, host sleep, and an iOS zoom gesture expose three boundaries the game still needs to design around.

  10. The first drafts were too long

    Three approved posts expose chronology, verification, and writing-style assumptions that the new blog workflow did not yet know to question.