For twenty years, the “Developer Experience” was a war against distraction. We treated the engineer’s focus like a fragile glass sculpture. The goal was simple: maximize the number of minutes a human spent with their fingers on a keyboard.
But as Michael Bloch (@michaelxbloch) recently pointed out, that playbook is officially obsolete.
Bloch shared a story of a startup that reached a breaking point. With the introduction of Claude Code, their old way of working broke. They realized that when the machine can write code faster than a human can think it, the bottleneck is no longer “typing speed.” The bottleneck is clarity of intent.
They called a war room and emerged with a radical new rule: No coding before 10 AM.
From Peer Programming to Peer Prompting
In the old world, this would be heresy. In the new world, it is the only way to survive. The morning is for what Bloch describes as the “Peer Prompt.” Engineers sit together, not to debug, but to define the objective function.
“Agents, not engineers, now do the work. Engineers make sure the agents can do the work well.” — Michael Bloch
Agent-First Engineering Playbook
What Bloch witnessed is the clearest version of the future of engineering. Here is the core of that “Agent-First” philosophy:
- Agents Are the Primary User: Every system and naming convention is designed for an AI agent as the primary consumer.
- Code is Context: We optimize for agent comprehensibility. Code itself is the documentation.
- Data is the Interface: Clean data artifacts allow agents to compose systems without being told how.
- Maximize Utilization: The most expensive thing in the system is an agent sitting idle while it waits for a human.
Spec the Outcome, Not the Process
When you shift to an agent-led workflow, you stop writing implementation plans and start writing objective functions.
“Review the output, not the code. Don’t read every line an agent writes. Test code against the objective. If it passes, ship it.” — Michael Bloch
The Six-Month Horizon
Six months from now, there will be two kinds of engineering teams: ones that rebuilt how they work from first principles, and ones still trying to make agents fit into their old playbook.
If you haven’t had your version of the Michael Bloch “war room” yet, have the meeting. Throw out the playbook. Write the new one.