Opinion · The Machine
The Model Is Not the Product
Every week a new model tops a new chart. The part nobody demos is the unglamorous scaffolding around it — and that scaffolding is still where the whole job lives.
Read the full storyClose the story
There is a particular kind of demo that has become the standard unit of excitement in this industry. Someone types a sentence, a model answers beautifully, the room makes a noise, and everyone goes home convinced the work is finished. I have watched a lot of these demos. I have given a couple of small ones myself. The thing I keep noticing is that the demo is always the easy ninety percent, and it is always presented as the hard one.
What the demo skips is everything that turns an impressive answer into something a stranger can rely on at nine in the morning without you sitting next to them. Where does the input come from. What happens when it arrives malformed, or empty, or in a format nobody anticipated. Who sees the output first. What does the person do when it is wrong — not philosophically wrong, just ordinary wrong, a name misread, a number transposed. How do they tell you. How do you find out before they do.
The demo is the easy ninety percent, and it is always presented as the hard one.
None of that is model work. All of it is product work, and product work is old. It predates every acronym currently on a conference badge. It is the same job that shipping any tool has always been: reduce the distance between what a person meant and what the machine did, then make the failure legible when the distance is too wide.
I think the confusion comes from how good the middle of the distribution has gotten. When a model handles the average case well, the average case stops feeling like a case at all — it feels like the product. So teams optimize the demo path, which is the average case wearing a suit, and then act surprised when the edges eat them. The edges always eat them. The edges are where actual users live, because actual users did not read your prompt guide and do not know what your system considers a well-formed request.
My working rule, learned mostly by doing it wrong first: the interesting question is never can the model do this. It is what does my thing do on the day the model is having a bad one. A tool that degrades honestly — that says it is unsure, shows its input, and leaves a human holding the wheel — is worth more than a tool that is right more often and silent about the difference.
That is not a fashionable position. It does not fit in a launch video. It is also, as far as I can tell from building small things and watching them meet real people, the entire job.
— Ends