Agentic Engineering
Moving from writing every line by hand to directing fleets of agents that do.
agentsworkflowcraft
For years the job was simple: I read a ticket, I wrote the code. The leverage came from typing faster and knowing more. That ceiling is gone.
The new job is closer to direction than authorship. I describe the shape of a change, hand it to an agent, and review what comes back. The skills that matter are different now:
- writing crisp specs an agent can't misread
- building tight feedback loops so mistakes surface in seconds
- keeping a mental model of the system that survives a thousand small edits
It rhymes with Building in Public - the work is legible by default, because an agent can only act on what you can articulate. See also Markdown as a Database for how I keep that articulation portable.
What stays human
Taste. Knowing which of three correct solutions is the right one. An agent will happily ship something that works and is wrong. Judgment is the moat.