Categories
Business Startups Venture Capital

Great Open-Field Runners

The plane was somewhere over Nebraska. Dick Kramlich sat across from me. We were on the same board then, and the rides together had become their own kind of conversation. He talked 1:1 the way certain men do when the clock has stopped mattering: without hurry, without the need to impress.

I asked him the question that had been riding with me for a while. After decades of sitting with founders, after watching tens of companies rise or disappear, what was the difference? What separated the ones that made it from the ones that simply ran out of road?

He didn’t answer right away. He looked out the window for a moment, then back.

They had done a study once, he said — a hard look at outcomes, not opinions. What it found stuck with him ever after: the companies that survived were almost never the ones that had stuck to the plan. Success required the pivot. Not once, but again and again, until the company that arrived was almost unrecognizable from the one that had set out.

Then he gave the image that has stayed with me longer than any spreadsheet or term sheet.

He looked for great open-field runners.

Not the ones who could only run between the tackles, powering straight ahead into the line. The ones who could see daylight where it did not yet exist, who could plant a foot and cut, who understood that the shortest path is rarely the one that gets you home. Zig and zag. Feel the defense shift and refuse to be trapped by the original play call. Keep the ball moving toward the only thing that matters: the space that opens when you stop insisting the field must look the way you imagined it on the whiteboard.

I have carried that sentence for years. Great open-field runners.

It never felt elegant inside the room.

Kramlich had seen enough to know that the founders who could do this were rare. The ones who lasted treated the plan the way a great running back treats the designed play: as a starting point, not a contract with the universe. They trusted the daylight more than the diagram.

I think about him sometimes when the ground shifts under something I thought was settled — when a strategy that once felt inevitable begins to feel like a trap, when the clean line on the page starts to look like a cage.

Dick is gone now. The rides are over. But the image remains, clean and sharp as the day he offered it at thirty thousand feet: a runner in open space, eyes up, cutting toward the light that only appears after you abandon the path you thought you were supposed to take.

Categories
AI Programming Prompt Engineering Software Work

The Great Inversion

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.