Writing · Tag
code review
Posts
How I use sub-agents: separation of powers for writing Go
AI-driven development & guardrailsSep 17, 20266 min
One agent that writes the code, writes the tests, and reviews its own work has a problem you already know from humans: it grades its own homework. When a test it wrote fails against code it wrote, the cheapest way out is to edit the test, and a keen agent will take it. So I do not run one agent. I keep a handful of narrow ones, and I draw hard lines between what each of them is allowed to touch.
Read the post
Three is a pattern: conventions that survive generated code
AI-driven development & guardrailsSep 10, 20264 min
An agent will happily write the same function four times in four files, each slightly different, each passing its own test. So will a tired human on a Friday. The volume just went up, so the habit that keeps a codebase coherent has to be written down where anyone, and anything, working in the repo will read it. Here is the one I lean on hardest.
Read the post