I Overheard AI's Entire Future in a Steakhouse Breakup
Field Notes from The Build – No. 3 || Strategy from the drafting table. Lessons from the keyboard.
I’d had the kind of week with Artwell where you either ship something or break something, and I’d managed both, occasionally to the same feature. I’d also spent it neck-deep in the debate eating every feed I follow lately: the one about AI and taste, about whether, now that the machine can make the thing, having good judgment is enough to make you a creator – or only a critic. So on Friday, fried on both counts, I took myself out for a steak.
Two tables over, a couple was having an argument, and it took me a full minute to work out what they were arguing about.
She’d said the thing was technically flawless and completely forgettable. He said she was being impossible – it was obviously high quality, look at it. She said quality wasn’t the same as good. He said that was a meaningless distinction. She said it was the only distinction that mattered. He said, and I’m quoting, “everybody’s suddenly an expert.”
It was, almost word for word, the argument I’d been reading all week. So I assumed I was eavesdropping on two people from my own corner of the world – that the debate had followed me out of my screen and into dinner. I was, I admit, a little impressed by their command of the material.
Then he delivered the closer: “If you think it’s so easy, I’d love to watch you cook it better.”
Ah. The steak. They were arguing about the steak.
Here’s the part that stayed with me, past the steak and past the secondhand discomfort of watching a date go sideways over doneness. I hadn’t misheard them. I’d heard them perfectly. The argument about the steak and the argument about AI are, line for line, the same argument. You can swap “the steak” for “the output” in every sentence either of them said and lose nothing at all. That isn’t a coincidence, and it isn’t because steak is secretly profound. It’s because both arguments are circling the same confusion, and neither side has bothered to name it. But I will try.
There are two different things we call “taste,” and they only look like one thing from a distance.
The first is the diner’s taste. You take a bite and you know. Too salty, the texture’s gone rubbery, the sauce is fighting the meat instead of helping it. You don’t need a chef’s jacket to register any of that, and the man’s “I’d love to watch you cook it better” was a bad move precisely because she never claimed she could cook it. She claimed she could tell it was gray in the middle. Those are not the same claim. She was right, and he reached for a credential to avoid admitting it. Anyone who has ever been handed “well, you’re not a chef” while pointing at an obviously overcooked steak knows the move. It’s a dodge. The diner’s verdict stands on its own.
The second is the chef’s taste, and it only shows itself when the plate is wrong and has to be fixed. The diner says “this is too salty.” The chef tastes the same bite and knows the saltiness is actually a fat problem, and the fix isn’t less salt, it’s a hit of acid to cut it. The diner can reject. The chef can correct. The distance between “this is off” and “here is the specific move that makes it right” is the entire job, and it’s the part you only get from having stood at the stove and ruined the dish a few hundred times.
Hold onto that gap, because the AI conversation lives or dies in it.
The loudest story in AI right now is a democratization story, and the optimistic version of it is genuinely true. The barrier to making things has collapsed. Anyone can generate a draft, a design, a working prototype, a passable first cut of almost anything, in the time it used to take to schedule the kickoff meeting. From there the discourse has converged, with remarkable speed, on a single comforting conclusion: since the machine now handles the making, the scarce and valuable thing left to humans is taste. Judgment is the new moat. Curators beat creators. The editor outranks the engineer. There are now four-part courses promising to train your taste in ninety days, as if taste were a certification.
And the first half of that is correct. When generation is free, discernment is what’s scarce, and the person who can tell the good output from the plausible one is holding something real. The couple at the next table had stumbled into the true half: you don’t need to be a chef to know the steak is overcooked.
But watch the move the discourse makes next, because it’s the same move the man made, just run in reverse. He took “you can’t judge it unless you can cook it” – false – and used it to win an argument he was losing. The AI conversation takes “you don’t need to be a chef to judge it” – true – and quietly extends it into “so you don’t need to be a chef to make it.” That sequel does not follow. And the reason it doesn’t follow is that when you build with AI, you are no longer the diner. You’re the one in the kitchen.
Think about what the machine actually is in this arrangement. It’s a line cook with flawless technique and no palate of its own. It will execute anything you can specify, instantly, without complaint, and it will re-plate the identical wrong dish all night because it cannot taste that the dish is wrong. At a restaurant, the diner’s “this is off” is enough, because there’s a chef back there with the second kind of taste who translates the complaint into a fix. In an AI build, there is no chef back there. There’s just the line cook and you. If all you’ve brought is the diner’s palate, you can tell the plate is wrong, but you can’t say acid-not-salt, so you send it back on a loop and get something differently wrong every time. The only thing that breaks the loop is the correction, and the correction is the chef’s.
There’s a reason the whole culture reached for “slop” to name what’s wrong with mediocre machine output – a feed-trough word the dictionaries crowned word of the year. We walked all the way into the kitchen to find the insult and didn’t notice we’d done it.
Here’s what that looks like from inside my own build, on a perfectly ordinary day.
Artwell turns long-form audio into clean, speaker-attributed transcripts and then into story. So transcription quality is foundational, and at one point I had two transcripts of the same recording sitting side by side. One of them looked obviously better. It came dressed with segments, summaries, topic tags, sentiment analysis – the whole garnish tray. The other was plainer. Word-for-word they agreed about ninety-six percent of the time, close enough that a quick look would call them equivalent and reach for the prettier plate.
The plainer one was the better transcript, and it wasn’t close. The fancy one had quietly turned “Puget Sound Energy” into “Pizza Time Energy,” and a neighborhood named SoDo into “So To.” Those aren’t formatting nitpicks. In a transcript meant to carry someone’s actual words into a published story, a confidently wrong proper noun is the gray center of the steak – the thing that looks fine under the garnish and destroys trust the moment anyone who was in the room reads it. Choosing correctly here was not “which output has more features.” It was knowing that for this product, quality means the words and the names survive intact, and the analytics layer is parsley. That’s not a verdict a diner’s palate can deliver. It’s a directorial call about what the dish is even for.
It happens at every layer. Another time, a fix to the audio-editing playback sailed through every check – tests green, types clean, lint quiet – and was still wrong, because it had bought its passing grade by making playback hesitate for a beat before it started, trading the immediate, responsive feel of the thing for technical correctness. Every box ticked. The dish still didn’t eat right. Passing the recipe is not the same as the plate being good, and no test suite has ever been able to taste the difference.
Now the uncomfortable part, the part those train-your-taste courses are selling around. The chef’s palate – the one that can direct, not just judge – is not built by curating. You do not develop it by assembling a reference library of great plates and studying them, any more than you become a winemaker by becoming a sommelier. The sommelier develops exquisite preferences by tasting. The winemaker develops judgment by making bad wine for years until it stops being bad. They are different organs, grown by different work, and only one of them can fix the batch. The judgment that lets me see past “Pizza Time Energy” came from two decades of being responsible for the finished thing – of shipping the wrong cut, watching it land badly, and learning in my hands what the fix actually was. It did not arrive on a schedule, and it did not come from watching.
Which is the quiet problem underneath the cheerful democratization story. We have declared judgment the most valuable thing in the economy at the precise moment we’re dismantling the work that produces it. The reps that used to build the chef’s palate – the grunt passes, the owned mistakes, the years on the line – are exactly the reps the machine now does for you. You can have the diner’s palate for free. The chef’s palate was never free, and it’s getting more expensive to acquire, not less, because the path to it is quietly closing.
I can’t reopen the path for everyone coming up behind me, and I’m not going to pretend a LinkedIn post does anything about it. What I can control is whether I keep doing my own reps. So here’s the thing I actually do, and it’s the reason my build process looks heavier than a solo founder’s “should.” The multi-session, multi-role orchestration I run – the planning panels, the forced checkpoints, the reviewer pass that exists only to argue with the implementer pass – is not only quality control. It’s a structure that keeps me at the stove. Left alone with a fluent line cook, the gravitational pull is to slide back into the diner’s chair: glance at the plate, looks plausible, ship it, send it back if someone complains. The orchestration is what stops the slide. It forces the second-order question every time – not “is this good,” but “what is this allowed to become, and where does it live, and what’s the one cut that keeps the product true.” It makes me direct instead of merely approve. In a world where the reps don’t happen for free anymore, I’ve built a way to keep doing them on purpose. It’s an apprenticeship for one, and I’m both the master and the kid sweeping the floor.
The couple never resolved it, for the record. He paid, stiffly. She was still right.
But the argument they were having is the one the whole industry is having, and it’s worth getting right, because the stakes aren’t really about steak or even about taste. The people who can build something good with AI are the ones who already spent the years at the stove – who carry the chef’s palate into a kitchen that now runs at impossible speed. The discourse is handing everyone else a flawless line cook and a diner’s palate and calling them chefs. And that works beautifully, right up until the plate comes back wrong and nobody at the table knows what to fix.
#Artwell #FieldNotesFromTheBuild #AIStrategy #SoloFounder