← Home

Category · Is vibe coding bad

Is Vibe Coding Bad? A Balanced Take for 2026

By Ethan Halfhide · Updated

"Is vibe coding bad" is one of the most searched questions in developer communities right now — and the answer depends entirely on what you are trying to build. Critics point to security holes, untestable code, and architectural debt. Proponents point to finished products shipping faster than ever.

The case against vibe coding

Critics argue that vibe coding bypasses fundamentals — leading to messy architectures, hidden security vulnerabilities, and code that is impossible to maintain without the original AI context. Stack Overflow and Hacker News threads are full of horror stories from developers who inherited vibe-coded codebases.

The case for vibe coding

Proponents argue that vibe coding is a tool, not a replacement for thinking. When used correctly, with human review at every step, proper testing, and iterative refinement, it produces real software that solves real problems. The proof is in the thousands of vibe-coded B2B apps already being used in production. If you are new to the debate, start with how vibe coding works and where the term vibe coding came from.

When it goes wrong

Vibe coding goes wrong when developers treat AI output as ground truth. Common failure modes:

  • →SQL injection from unsanitised inputs
  • →Hardcoded secrets committed to git
  • →Unoptimised database queries that work locally and kill performance at scale
  • →No tests, so regressions go unnoticed until production

When it works

Vibe coding works best for greenfield projects, internal tools, MVPs, and solo-founder SaaS. The apps in this directory were all built by non-traditional developers, and real businesses are paying to use them. It also fits internal tools over business data, which our Salesforce vibe coding guide covers, including where the approach falls short.

Vibe-coded apps shipping in production

⚡ Quick pick

Expensinator: Production expense manager vibe-coded with Lovable. Proof that AI-built apps can be reliable enough for paying customers.

1
Expensinator logo

Production expense manager vibe-coded with Lovable. Proof that AI-built apps can be reliable enough for paying customers.

2.5
vibe
2
Dealflow CRM logo

A working CRM tracking real sales pipelines, vibe-coded with Bolt.new in a weekend.

2.4
vibe
3
Schedsy logo

Appointment booking with payments built in Cursor — used daily by service businesses.

2.3
vibe
4
ProposalKit logo

Freelance proposals and contracts built with Lovable. Real users, real revenue.

2.3
vibe

Frequently asked questions

It can be, if you ship AI output without review. Common issues include unsanitised inputs and leaked API keys. The fix is treating AI output the same way you would treat a junior developer's PR — always review before deploying.

Yes. Many directory-listed apps are live in production with paying customers. The key is iterative development: build a feature, test it, review the code, then ship.

Yes — with realistic expectations. Vibe coding lowers the barrier to entry dramatically. Beginners should start with simple projects, read the generated code, and build their understanding alongside the tool.

Keep exploring

About the author

Ethan Halfhide

Ethan Halfhide is an AI technologist and educator who has taught more than a thousand founders to build apps with AI coding tools. He tracks Lovable, Cursor, Bolt, Replit and the apps people ship with them.