Design for the API call you cannot take back
An API with create but no delete changes where your guards live. Four checks that run before the request, and the one that only exists because a create returns 201 on the wrong target.
All posts
Telling an AI agent your rules does not make it follow them
Seven guards fired on me in one session, each blocking a command I had already decided was fine. That gap between deciding and being allowed is the whole argument for hooks.
100 technical posts, and the gates that stopped them being slop
Publishing at volume with an AI agent is easy. Publishing at volume without shipping slop needs machinery that refuses, and refuses loudly.
Every action your AI agent takes should be safe to run twice
Agents retry after ambiguous failures, so every action needs to be safe twice. Ledgers, content checks and dry runs — and the create that is genuinely not idempotent.
Read the status code before you believe the README
Six documented endpoints, two that work. Probing an API's real surface takes a minute and changes the architecture you build on top of it.
The command that leaked a secret was not cat
I leaked an OAuth token by running a command designed to print only field names. The file was malformed, so the field name was the secret. Verb denylists cannot catch this shape.
A stale doc does more damage than a missing one
Documentation that is confidently wrong is worse than absent, because it stops the investigation. Three examples from one codebase and what made them survive so long.
Why every command runtime is capped at 200 lines
A 200-line cap on command runtimes, enforced by a hook. What it rejected, what that forced, and the one time the cap was the wrong tool.