There's a line near the end of the Pixar movie Ratatouille that I keep coming back to lately. The food critic Anton Ego, after eating Remy's ratatouille, sits down and writes his review. He says that Gusteau's motto, "Anyone Can Cook," was always misunderstood. It doesn't mean everyone can be a great chef. It means a great chef can come from anywhere.
I've believed that about software for a long time. Long before AI could write a for loop.
I've spent years encouraging people without a technical background to try coding. Not as a party trick, but because I genuinely believe the skill is learnable by more people than the industry wants to admit. I've pushed teammates to pick it up. I've seen it click for people who had no business, on paper, becoming developers. And one of the most technically sharp people I've ever worked for never finished college. His instincts were better than people with CS degrees I've met. So yeah, I came into this whole AI coding conversation with a pre-existing opinion: the gate has always been too narrow.
What's happening right now with vibe coding and AI tools is just the latest version of that argument. And people are still having it wrong.
The Argument People Are Having
If you spend any time in developer circles, you know the vibe. Tools like Cursor, GitHub Copilot, and Claude have kicked up a real culture war. On one side, you've got people saying this is the democratization of software. Anyone can build now. Non-technical founders can ship their own MVPs. Designers can prototype without a developer. The barrier is gone.
On the other side, you've got experienced developers rolling their eyes. "These AI-generated apps are a mess under the hood." "Nobody understands what they're shipping." "Give it six months and the tech debt will be unmanageable." "Real programming requires real skills."
Both sides are kind of right. And both sides are missing the point.
What Vibe Coding Actually Is
Let's be honest about what vibe coding is in practice. You describe what you want, the AI writes the code, you poke at it until it works, and you ship it. You might not fully understand every line. You're leaning on the model to make decisions you don't have the background to make yourself.
For small, contained projects, this genuinely works. People are building real tools, real products, real things that solve real problems. That's not nothing. That's remarkable.
But here's the thing that doesn't get said enough: the output is only as good as the person directing it. The AI is Linguini. You're Remy.
If you've seen the movie, you know Linguini can't cook. He's clumsy and clueless in the kitchen. But he has Remy guiding him, and together they produce something extraordinary. The catch is that Linguini has to trust Remy, stay out of the way at the right moments, and rely on Remy to guide him properly. Remy has to pay attention, taste/test things, and make sure they are on the right path to a great outcome.
That's the vibe coder who succeeds. They care. They pay attention. They test things. They ask good questions. They know enough to recognize when something is wrong, even if they can't always fix it themselves.
The vibe coder who fails? They're just mashing buttons and hoping.
The Ego Problem
Here's where the other camp gets it wrong.
There's a version of the experienced developer critique that's basically just Anton Ego in the first half of the movie. Gatekeeping dressed up as standards. "You didn't go to culinary school, you don't belong in the kitchen." It ignores the fact that some of the most interesting software being built right now is coming from people who a year ago couldn't have shipped a line of code.
I've seen this my whole career, honestly. The instinct to protect the craft by protecting the club. And I get it, experienced developers have real knowledge worth protecting. The complexity of building systems that scale, the hard lessons about what breaks under pressure, the judgment that only comes from having been burned a few times. That's worth something.
But the boss I mentioned earlier, the one without the degree? He had all of that. He just got it a different way. The credential was never the point. The thinking was the point.
Ego's problem wasn't that he had high standards. His problem was that he'd stopped being open to surprise.
What the Analogy Actually Tells Us
Gusteau's motto didn't mean the standards don't matter. Remy still understood flavor, technique, and balance better than almost anyone. The standards were still there. The gatekeeping was what was wrong, not the craft.
Same thing here. Good software still requires clear thinking, careful architecture, and an understanding of what can go wrong. AI doesn't change that. What it changes is who can develop those instincts and how fast they can get there.
A motivated non-developer using AI tools will ship something mediocre at first. That's fine. That's how everyone starts. Those who stick with it will start to develop a real taste. They'll notice when the generated code is repetitive or fragile. They'll start asking why, not just what. They'll start caring about the structure, not just the output.
That's how a great developer can come from anywhere. Not because the tools lower the bar, but because they lower the entry cost to a place where the real learning can start.
So Where Does That Leave Us?
If you're an experienced developer, the move is not to dismiss vibe coding. The move is to understand what it's good at and what it isn't, and position yourself accordingly. AI handles a lot of the boilerplate, the syntax, the plumbing. The work that remains is judgment, architecture, and knowing what questions to ask. That's not a threat to good developers. That's a promotion.
If you're a newcomer using AI tools to build things, take it seriously. Don't just ship and forget. Read the code. Ask the AI to explain what it did and why. Break things on purpose to see what happens. The goal isn't to stay Linguini forever. The goal is to eventually understand what Remy is doing.
And if you're still out there insisting that only "real" developers who learned the hard way have any business building software, well. Ego had that position too.
And then a rat made him cry with a plate of vegetables, and he had to rethink everything.
Anyone can code. That doesn't mean everyone will be great at it. It means the next great developer can come from anywhere.