Matt Van Horn (@mvanhorn) on X
Cody and Justy dig into Matt Van Horn's viral post about 'WTF Is a Loop?' — the Peter Steinberger vs. Boris Cherny debate that had AI coders repeating a six-word phrase nobody can define. Cody argues the term is becoming meaningless buzz; Justy sees a real product signal in the confusion itself.
Transcript
Justy Cody, have you been watching this whole Loop argument that ate the timeline this week?
Cody Yeah, I saw the Matt Van Horn post. Three and a half million views on a thing where nobody can define the word they're fighting about. Pretty on-brand for AI Twitter.
Justy I mean, that's kind of the point though? Peter Steinberger and Boris Cherny are both smart, and they're genuinely talking past each other about something real.
Cody Sure.
Cody But that's exactly my problem with it. The six-word sentence everyone's repeating — and I won't even say it because it's become this empty incantation — it sounds profound until you poke at it and realize 'loop' means five different things depending on who's typing. Is it a retry? An agentic cycle? A human approval step? Those are not the same concept.
Justy Okay but Cody, you're doing the classic thing where you dismiss the buzzword and miss the signal. People are fighting about this because the confusion is real. Like, teams are actually shipping features where they don't know if the human should approve every step or if the model just runs.
Cody Right, right.
Cody And that's a fine debate! But calling it 'the loop' obscures more than it reveals. Steinberger's side seems to be about tight feedback — human sees what the model did, corrects, model tries again. Cherny's side is more like, let the model run until it hits a trust boundary, then check in. Those are two different architectures, and mashing them into one word is how you get three and a half million people nodding along to something they can't operationalize.
Justy I think you're right that the word is doing too much work. But the fact that it's doing too much work is interesting from a product standpoint. When that many people glom onto a term they can't define, it usually means there's a latent need that doesn't have good language yet. Like when everyone said 'serverless' for two years and it meant everything and nothing, and then it eventually narrowed into something specific and useful.
Cody Mm-hm.
Cody I'll give you that — 'serverless' went through the same cycle. But the difference is that serverless eventually converged because the constraint was technical. You could point at a runtime and say, that's what I mean. A 'loop' in AI coding is a control-flow decision, not a runtime. It's a design choice about where the human sits, and that's way more context-dependent. I don't think it converges the same way.
Justy That's actually a fair distinction. The control-flow thing matters because it's not just one decision — it's a decision that changes based on what the model's doing, how reliable it is for that task, how much the user trusts it. So the word might fragment into a family of terms instead of converging.
Cody Exactly.
Cody And that's what makes the Steinberger-Cherny thing kind of frustrating. They're both right for different contexts, but the framing turns it into this either-or when it's really a spectrum. Some tasks you want tight human-in-the-loop, some you want delegated autonomy with checkpoints. The word 'loop' papers over that whole decision space.
Justy Okay, I'll concede that the word is probably doomed. But the need it names? That's not going anywhere. Teams are building this stuff right now and they need vocabulary, even imperfect vocabulary, to coordinate. If 'loop' gets them talking, that's step one.
Cody Step one of what though? Because step two is usually someone builds a product around the buzzword before anyone's nailed down the semantics, and then you're stuck with a dashboard that says 'loop count' and nobody knows what it's counting.
Justy That is very specific and probably accurate.
Cody I've seen it happen. It's the same move as every other hype cycle. The word becomes a feature checkbox before it becomes a specification.
Justy Alright. So here's where I think we actually land. The word 'loop' is a mess, you're right. But the tension it's pointing at — where does the human sit in an AI-assisted workflow — is maybe the defining product question for coding tools right now. And Steinberger versus Cherny is basically the two poles of that debate made flesh.
Cody Yeah, I can agree with that framing. The argument is real. The term is just… not ready to carry the weight people are putting on it.
Justy So the honest verdict is: stop arguing about the word, start arguing about the trust boundary. Which, honestly, is the more interesting conversation anyway.
Cody That I'll sign up for. The trust boundary question has actual answers. The loop question just has vibes.
Justy 'Just has vibes' — that's going on your tombstone, Cody.
Cody It probably is.
Justy Anyway. If you're building coding tooling right now, figure out which side of that trust boundary your product lives on. Don't just slap 'loop' on the landing page and call it done.
Cody Agreed. And if you want to go deeper, Van Horn's original post links through to both sides of the argument. Worth reading the actual positions, not just the quote tweets.
Justy Yeah. Okay, I think that's enough vibes for one Tuesday. I'm going to go get more coffee.
Cody Get me one too.
Justy You're in DC. Get your own coffee.
Cody Fair enough.