The Agent-Shaped Codebase
Codebases are about to be read more often by agents than by people. That changes what "clean code" means.
Everything filed under Agentic Development — essays, notes, playbooks and signals.
Codebases are about to be read more often by agents than by people. That changes what "clean code" means.
When generation is free, the scarce resource is judgement. That reframes what a senior engineer is for.
An honest list, kept up to date, of where the end-to-end agentic workflow still falls over.
The README was written for a human who would skim it once. This file is read in full, every run.
Half-formed thought on why "just paste more" stops working past a certain repo size.
Unfinished abstractions are worse than none, and agents make them cheaper to create and harder to spot.
A running wishlist. Mostly about observability and being able to stop the thing mid-flight.
Every tool definition costs tokens on every turn. Most agent slowdowns are a context problem, not a model problem.
The signals we used to judge competence — clean code, fast output — no longer carry information.
The clearest public writing on when an agent loop beats a fixed workflow.
An argument that agents should use the tools humans already use, rather than getting bespoke ones.
On treating low-quality agent output as an engineering problem rather than a model problem.
If the model is faster than your CI, your CI is now the product constraint.