Tag: engineering

  1. No. 014

    A one-word Claude Code call read 236K tokens

    I switched off every built-in tool on a headless Claude Code helper to make it cheap, and its one-word answer read 236K input tokens, seven times the default. The cause was MCP tool schemas, the fix was one flag, and it started a month of measuring what an agent carries into every turn.

  2. No. 012

    systemd said active through 128 crashes

    In July I learned to let a broken process crash so its supervisor could restart it clean. In November that same restart hid 128 crashes of my box watcher. Four months of mistaking running for working.

  3. No. 011

    What my coding agent briefs forgot to name

    Five weeks of handing jobs to Codex and Claude workers, and what each failure taught me a brief must name: where to write, which files, when it is done, and how the answer gets back.

  4. No. 010

    My slow test gate hid its own failures

    My push checks grew from 19 seconds to nearly two hours in seven weeks. Time limits, idle connections and even the failure report turned that wait into silence, until a 71-second check found what the full gate only reached at minute 70.

  5. No. 009

    My tests kept agreeing with me

    653 unit tests passed and a real git push still walked straight past my pre-push hook. Again and again over six weeks my tests agreed with my own assumptions instead of the real input, from a hosted test runner to model output and a fixed clock.