Field notes on agentic development
Building software where the agent does the typing.
I write down what actually happens when real engineering work is handed to an agent - the harnesses, the context budgets, the failed runs, and the numbers that come out. Not demos. Not the launch-day thread. The part that survives contact with a codebase.
Latest notes
All writing →12 NOVThe verification gapWriting code got cheap. Knowing whether it is correct did not. That asymmetry is now the whole job.05 NOVContext is a budget, not a promptEvery token in the window costs money, latency, and attention. Treating it as free is why agents get worse the longer they work.24 OCTThe harness matters more than the modelSame model, different harness, different result. The wrapper is where the compounding happens - and it is the part you can actually control.
EXP-001EXP-001 - Porting 151 posts off a Next.js blog with an agentAn agent can migrate a 151-post legacy blog to a static site with full URL preservation and zero content loss, if the migration is decomposed into crawl → normalise → verify instead of attempted as one task.running16 NOVEXP-002EXP-002 - Does a written plan file actually improve success?Committing a plan file before implementation raises first-pass success on multi-file refactors, and lowers the human review time per merged change - even when the plan is later wrong.idea10 NOV
Patterns
Browse the catalog →01 / corePlan as artefactThe agent writes the plan to a file in the repository, before writing any code, and the human gate happens there.1 minread →02 / coreContext budgetAllocate the window deliberately across layers - instructions, project facts, working set, history - instead of filling it until it overflows.1 minread →03 / coreTests the agent cannot authorWrite the acceptance test yourself, run it before the code exists, and never let the agent weaken it to go green.1 minread →04 / coreSeparate author and reviewerA second agent with a fresh context reviews the diff against the task, not against the author's reasoning.1 minread →05 / coreBlast radiusConstrain what a run can touch, so that a wrong answer is cheap to roll back rather than expensive to discover.1 minread →06 / supportingCheckpoint and resumeWrite progress to a file as you go, so a dead session is an inconvenience instead of a restart.1 minread →
Before the pivot
Open the archive →From 2023 to early 2026 this site was a system-architecture notebook - Java, security, microservices, the occasional piece about burnout. 151 of those posts are still here, indexed and readable, under /archive. They are no longer what this place is about.