From "show me your code" to "show me your idea"

From "show me your code" to "show me your idea" Or: the abdication is signed, and the court is empty 2026-07-13 Second in a six-part series on what building with AI agents did to one developer. This piece is where code loses authority — and the question becomes what can still pin "this is what I meant." Last week someone turned a laptop toward me. A function on the screen, comments neat, tests green. He pointed at a line and said: this is what I meant. I asked: is that what you meant, or what the model smoothed into place? He froze. I froze. Three seconds opened in the air that neither of us would fill. In those three seconds I counted two thoughts. First: I shouldn't have asked. Second: who else is left to ask. Fingers on the trackpad edge — the heat was the machine's, not an idea's. Two people facing the same green, neither daring to hit Enter. It wasn't supposed to be like this — I thought. There used to be a tyrant: compiler, tests, exit codes. Talk is cheap, show me the code. Pretty talk died where the run failed. Drop the brick; fakes rang. After the ask you could stand across an exit code — a piece of iron in the middle that would not lie. The brick is still there. He pushed it over. The authority is gone. Running is no longer the same as "this is what you meant." The prettier the sample, the more the questioner looks like a nitpicker. And you still can't drop the question — drop it, and you pretend that running is the same as "this is what you meant." So some people bring it back: show me your talk. More meetings, spell it out, align the narrative. Talk was always cheap. I always took it for empty speech — time burned, energy burned — which is why I would rather stake the final court on code. Code lost its authority. I do not want that road back. So the ask shrinks to: show me your idea. Not inviting talk back in — wanting something that can still be pinned: a tradeoff, a fork, whose fault if wrong. Open your mouth, and it becomes talk again. Models say it too, often smoother. The waste I hated most came back in a different shirt. I am still beside him, trackpad heat still on my fingertip, not knowing whether to say "I believe you" or "prove it again." Both feel wrong. Swallow; throat goes dry. Two days later I asked him again. Softer: not "did you mean this," but "why write it this way." He answered fast. Boundaries first, then retry on failure, then why not the other path. Clean. I almost convicted him again for being too smooth. When he finished, I changed the knife — not restatement, a fork: "If the retry budget is cut in half, what breaks first?" He stopped. Not the pause of swapping connectives. After the stop, he named something that had not appeared in the first speech — the order of cache invalidation. That inch was his. A model can answer a fork too, often more completely. I asked again: if we do it in the order you said, which step blows up first online — which sentence do you own? He pointed at the one he had just spoken. That point mattered more than answering completely. I had been measuring wrong: smooth is not evidence of guilt; standing behind the fork is. I asked myself the same way. At night, facing a stretch I had just "written" — I had clicked Accept. The comment announced intent. I wiped the whole intent block, stared at the blank for a long time, then typed. What came out was almost as smooth as what I erased. Smooth enough to sicken me. Deleted again. Typed again. The third pass was still smooth. Finger on Save, I thought: if it writes smooth, does that mean it isn't mine. No. Reaching the same logic a second time can be called understanding. What I feared was not smooth — it was having no fork I could answer, while still using "I hesitated" to prove it was mine. I added a fork in my head, answered it poorly, and still pressed Save. The cursor moved on. I did not become more myself, or less. Later I thought: asking can move a person and still fail to pin a lie, so nail. Nail every claim into something that runs and shows a side effect. One night I nailed eleven. The ninth went red. I fixed it, ran again, red to green. While fixing, my hand was hot — briefly, like heat on loan. When all eleven went green, the terminal lit in a row. I sat with that row and waited for "this is what I meant" to sound inside. It didn't. That sit cleared the old books. An exit code only ever proved one thing: it runs. It never proved "this is what you meant." We treated those as the same passport and called the illusion rigor. The model did not remove the final court — it tore the illusion open. The green was steady. "This is what I meant" still did not sound. Nails can pin a lie. Nails cannot pin whose idea it was. I did not close his laptop. I did not rewrite that comment for him. The cursor still blinks after "this is what I meant." I no longer expect it to testify for anyone. What I can require is only a sentence that can bite me later: which tradeoff I own, and if it is wrong, it is mine. That sentence can live in a PR, or only in the mouth. What matters is not a tidy format — it is whether a person will still stand behind a choice. Those three seconds ended in stopping — stop asking green to prove both "it runs" and "this is what I meant." Previous in this series: The Mirror Cannot Reflect Thought · To follow: Judging Fatigue — From Verifying AI to Verifying Myself · The Boundary of the Harness · A Reviewer Nailed Me in Six Places