The IP is the guy in the chair
The tool could build anything I could specify. It could not tell me I was specifying the wrong thing.
The code is a commodity now and it gets cheaper every month. What is not a commodity is knowing the business well enough to feel that the reports were a symptom, back up three steps, and re-aim the entire build.
These tools are unbelievably good once the frame is right. Somebody still has to know when the frame is wrong.
THE HONEST VERSION
It catches its own mistakes, constantly
Claude Code did not see the pattern before I did — I had to argue with it for a while, and once it understood what I was saying it ran with it and helped me rebuild absurdly fast. But the honest version is more useful than the clean one: it catches its own mistakes all the time. This week it put an arrow pointing the wrong way on every row where up is bad, and separately dropped seventeen sparklines by reading one field of a payload instead of five. It caught both of those itself.
THE ORACLE
Nobody handed me the oracle
It only caught them because there was something to grade against. I had decided the morning report was the reference — the thing every other view has to agree with. Give it an oracle and it will correct itself all day long. Choosing what gets to be the reference, and being right about that choice, is the judgment.
WHAT IT MEANS
You cannot buy it or install it
I am not a software engineer and I do not want to be one. But I know what needs to get built, because I have spent years living with the consequences of getting it wrong. That means knowing what a customer actually is here, that how we define churn matters more than whatever model predicts it, which of our systems lies and in which direction, and the difference between a question that sounds important and a question that changes what we do on Monday morning. You cannot buy that, hire it quickly or install it. It comes from being the one responsible for the outcome.