Rethinking engineering in 2026
Running coding agents in parallel, I've watched the bottleneck move. It's less about writing the code and more about how quickly I can give clear direction, review what comes back, and make decisions. The agents can keep working. When everything needs my attention, I'm the queue.
That's what agent-first engineering means to me: rethinking the workflow around where the bottleneck is now. Clear guidelines, checks agents can run themselves, and human review where it matters—not human approval at every step. My role isn't gone. It has moved, and the way I work needs to move with it.
This site is me thinking in public. Some of what’s here are really simple ideas; others I’ve turned over for several weeks before writing them up. Publishing them is how I share them, and how I keep a trace of what I thought and when—so I can come back and see what held up.
Claims about the world carry a citation. Opinions are marked as mine. When an agent wrote a passage it is marked, because that distinction is the point.
Skills
The skills behind the agent pipeline are published on this
site as Agent Skills, at
the well-known discovery path: writing and reviewing specs, reviewing code
for security, UX, performance and data, and drafting and reviewing launch
announcements. Install them with
npx skills add https://code.benoitguivarch.fr, or by hand as
described in
the
spec post.