Is Vibe Coding Bad? When It Works and When It Bites

Is vibe coding bad? No, not as a way to prototype, learn, or build throwaway tools. It starts to bite in production when you skip the review, and the bill often shows up as vibe debugging. A balanced verdict, plus 65 AI shirts from $34.95.

||7 min read
A person at a developer desk wearing the Code Culture Vibe Coding 2 Hrs Vibe Debugging 20 Days shirt
JOURNAL · DEVELOPER CULTURE · 2026.11
is vibe coding actually bad?

It is fine for a Saturday prototype. It gets expensive when you have to vibe debug the thing you just shipped.

Is vibe coding bad? No, not as a way to prototype, learn, or build throwaway tools. It starts to bite when the app has to live in production, hold real data, or be debugged by a human who never read the diffs. The honest cost often shows up as vibe debugging: a short burst of prompting, then a long cleanup.

The short verdict

The question people type into Google is "is vibe coding bad," and they want a yes or a no. Software does not work like that. The method is a way of prompting an AI until the thing seems to work, often without reading the code. That habit is great on a Saturday. It is a poor way to ship the system you will still be on call for on Monday.

If you want the origin story and the culture around the term, that already lives in our what is vibe coding guide. This post is the verdict: when the habit is fine, when it bites, and why the cleanup has its own name.

When vibe coding is fine

Use it when the stakes are low. A personal script. A first pass at a landing page. A toy that can die at the end of the weekend. You are trying to find out whether an idea is even interesting, not whether it can survive a real user with a real credit card.

Salahuddin Azad and Ritesh Chugh, writing in The Conversation on July 29, 2026, make that cut clearly. They call vibe coding an excellent way to experiment, learn programming concepts, or quickly build personal tools. Entrepreneurs can prototype. Hobbyists can automate the boring parts. The trouble starts, they write, when software that appears to work is treated as ready for real-world use simply because it runs.

That is also why the joke shirts exist. The I Don't Write Code I Write Vibes Shirt is weekend mode, printed on purpose. Keep it for the work that is allowed to be messy.

When it bites

The failure mode is familiar: you accept a 400 line diff because the summary sounded confident, a test disappears because it was failing, and three days later you cannot explain the change. In a March 2025 interview with Ars Technica, Simon Willison said, "Vibe coding your way to a production codebase is clearly risky." Most of the work, he added, is evolving existing systems, where the quality and understandability of the code still matter.

The ACM Technology Policy Council's April 2026 TechBrief makes the same point in drier language. Vibe coding can speed the work and make software easier to start. It also often skips the practices that keep a system secure, reliable, and possible to maintain. People, not the model, stay responsible for what the code does.

This is not a new genre of horror story. We already collected public production failures in Vibe Coding Works Until It Doesn't. This post will not retell those incidents. They are the evidence that "it ran on my machine" is not a release checklist.

The Agent Is Possessed Shirt in black, flat lay product photo

WEAR THE JOKE

The Agent Is Possessed Shirt

You left it running. The folders can confirm.

From $34.95

The research is not kinder. In a July 2026 ICML paper, Zhao and colleagues built SUSVIBES, a benchmark of 186 real-world feature requests taken from projects where humans had already shipped vulnerable code. They tested 12 coding-agent setups. SWE-Agent with Claude 4 Sonnet was functionally correct on 57% of solutions, and secure on only 11.8%. Prompting the agent with vulnerability hints did not fix it.

Even the culture has started to flinch. On November 4, 2026, Tim (@LuftkoppTim) quoted a flashy interface clip and asked, "can Apple stop vibe coding please." The joke is the unease: if this is how software now gets made, do we actually want it everywhere?

Vibe debugging: 2 hours, then 20 days

"Vibe coding: 2 hours. Vibe debugging: 20 days." Kainat (@founder_kai) on X, November 8, 2026

That line is the whole cost model, written as a joke. You spend an evening prompting. You spend the next three weeks trying to understand what you accepted. Kainat asked the obvious follow-up: do you actually vibe debug, or do you just ship the pretty-faced vibe code?

Vibe Coding 2 Hrs Vibe Debugging 20 Days Shirt in black, flat lay product photo

WEAR THE JOKE

Vibe Coding 2 Hrs Vibe Debugging 20 Days Shirt

The timeline nobody puts in the sprint.

From $34.95

We printed the timeline because it was already a shirt waiting to happen. The Vibe Coding 2 Hrs Vibe Debugging 20 Days Shirt is the chart. The I Vibe Coded It Now I Vibe Debug It Shirt is the status update. The Vibe Debugging Receipt Shirt itemizes the hours you did not plan.

Vibe debugging is not a separate methodology. It is what happens when the first pass skipped the reading. The fix is boring on purpose: read the diff, write a test the model did not invent, and keep a human on the hook for the merge. The AI Assisted Human Supervised T-Shirt is that job title, in case anyone in the standup still needs a reminder.

The Vibe Debugging Merch Board: 6 Designs Developers Pick First

Tap any shirt to see sizes and colors.

More picks from the collection

Gifts for the person still debugging

If you are buying for the teammate who now spends the week cleaning up a two hour prompting session, buy the shirt that names the work. The AI & Machine Learning collection has 65 designs, with tees from $34.95. It works for a birthday, a new-job gift, or the person who caught the bad patch before it shipped.

The practical bits: free shipping on 3 or more shirts, which is orders of $85 USD and up, worldwide. Build time is 2 to 5 business days because each shirt is made to order. Quality issues get a 30-day free replacement. There are no change-of-mind returns, except where the law requires it. Check the size chart on the product page before you order.

Frequently Asked Questions

Is vibe coding bad?

No, not as a default setting for every project. It is a good way to prototype, learn, or build a throwaway tool. It becomes a problem when the app has to live in production, hold real data, or be maintained by someone who never read the diffs.

When is vibe coding fine?

When the work is low stakes: a Saturday experiment, a personal script, a first look at an idea. Salahuddin Azad and Ritesh Chugh make the same cut in The Conversation: the method is excellent for learning and personal tools, and the risk rises when apparently working software is treated as ready for real use.

What is vibe debugging?

Vibe debugging is the cleanup that follows a fast prompting session, when you have to understand, test, and fix code you did not really read the first time. In a November 8, 2026 post, Kainat put the joke on a clock: vibe coding took 2 hours, vibe debugging took 20 days.

Is vibe coding safe for production?

Not if you skip review, tests, and security checks. Simon Willison has said vibe coding your way to a production codebase is clearly risky, because most professional work is evolving existing systems that have to stay understandable. For documented production failures, read our earlier post on vibe coding production fails.

Related reading: What is vibe coding?

0 comments

Leave a comment

Please note, comments need to be approved before they are published.