In Defense of Vibe Coding

Let them build. Just maybe… don’t launch it yet.

There’s a debate heating up in dev circles—one that’s quickly climbing the ranks of the classics like “Should designers code?” or “What even is a full-stack developer?

Enter: Vibe Coding.

For the uninitiated, vibe coding is the idea that anyone—literally anyone—can open up a code editor powered by an AI agent (like Cursor) or use a tool like Bolt.new, Lovable, or any of the other AI-powered builders out there, and start prompting their way toward a working app or interface.

On the surface? Amazing. It gives people the ability to build products without writing a single line of code. They can tinker with UX, try different layouts, test their ideas—all without spinning up a dev environment or learning what a div is.

Now here’s where people get weird about it.

The pushback is almost always about “best practices.” That it produces “bad code.” That it doesn’t scale. That it’s dangerous.

To that I say: It’s not supposed to be perfect.

And it’s not trying to be.

I’m a senior-level front-end dev. I own a dev agency. And I use vibe coding all the time. Not because I don’t know how to code—but because vibe coding lets me actually start something. I have dozens of product and app ideas in a backlog, and now I can riff on those ideas quickly—see if the concept has legs, without committing weeks of development time.

It’s like sketching.

You don’t oil paint your first draft.

Vibe coding is the pencil sketch. You draw, erase, redraw, trace over lines. Then—if the composition is strong—you switch tools. Maybe it becomes a pastel, or an acrylic. Maybe it just stays a sketch.

In our workflow, we vibe code until we’ve got something promising. Then we “eject” it—pull the code into Cursor, into a proper repo, and finesse it. That’s where the engineering kicks in.

We know when the vibe is off.

We know when to toss bad AI code.

We use it, but we control it.

Is vibe coding ready to build HIPAA-compliant enterprise software? Of course not. But should it be a safe space for creators—technical or not—to explore ideas, build MVPs, and validate direction?

Absolutely.

The tools are only going to get better. But the goal isn’t perfection. The goal is progress.

So yes—let people vibe code.

Just remind them:

With great power comes great… console.log()‘s?

Happy vibe coding.