The Coach Who Plays
There is a version of this argument that sounds reasonable on its face.
The coach was once a player. A good one. And now, with AI-driven development compressing the cost of execution, the question gets asked: if implementation is nearly free, why wouldn't someone who can both design and build do both? Why draw a line at all?
The answer is not about capability. It is about where the eyes need to be.
A coach who steps onto the field stops being a coach. Not because they lack the skill to play — but because playing and watching are incompatible states of attention. The moment you are in the action, the whole is no longer visible to you. You see your immediate vicinity. You make local decisions. The shape of the game, the drift of the second half, the pattern forming three plays ahead — that requires distance.
This is what gets lost when the designer also implements.
It is not the time, exactly, though time is part of it. It is the mode of attention. Design judgment — what to build, in what order, what to leave out, what will break in six months — requires a kind of peripheral vision. You are holding the whole structure in mind while evaluating any single part. Implementation pulls attention toward the particular: this function, this edge case, this test. The two are not impossible to alternate. But they are not free to combine.
The objection worth taking seriously is this: a coach who has never played cannot earn the trust of players. Presence on the field, even briefly, signals understanding. And there is something to this. Credibility matters. A designer who has never shipped anything is working from abstraction.
But there is a difference between having played and playing now. The knowledge transfers. The attention does not need to.
AI-driven development has sharpened this distinction rather than dissolved it. When execution accelerates, the bottleneck moves. What takes time now is not writing the code — it is deciding what the code should do. The demand for design judgment increases precisely because implementation is faster. Which means the cost of splitting that attention has gone up, not down.
The coach who plays is not wrong to play. They may be the best player on the field.
They are just no longer watching the game.