Vibe-coded software is junk food

I was thinking about this while cooking some meal. I'm not good at it, so I try to follow a recipe. I use fresh ingredients, wash and chop them carefully, watch the boiling pan oftenly so I don't overcook. Maybe too often, because I don't really know what I'm doing. The result isn't necessarily great, but it's better than fast food, industrially processed food and sometimes even restaurant delivery. The reason is that I care, while someone in fast food would probably not. (Well they care that I don't die eating it, but they don't care that I'll be overweight 5 years from now.)

Unlike cooking, I know a thing or two about software. I'm long past the delusion of greatness, but I'm a decent engineer and I usually know what I'm doing. But when I work on something, if the result is any good, it's for the same reason: I care.

Vibe-coded software is like junk food, because the AI doesn't care. Maybe worse: it doesn't even think. For this main reason I believe that companies which allow too much AI-generated code into their production systems might have some major health issues in the long run.1

I have seen projects having tens of thousands of lines, created in record time. Definitely impressive, but it's humanly impossible to review all that code. What if there's some fundamental flaw lurking somewhere, which can ocasionally do something catastrophic like wiping out databases or filesystems? Or maybe worse, silently slipping inaccuracies in production data for a long period of time? You can only hope there isn't.

Human-made software should be trusted more than AI-generated software simply because someone cares about it. Most programmers I know even care about their code beeing fast and beautiful (besides just doing the job), to the extent afforded by their experience. But AI doesn't care; it says “you are absolutely right, let me try that again” after doing the dumbest shit possible. AI won't lose its job, AI won't get divorced, won't lose family, won't get sued; whatever things people care about, AI isn't affected.

I'm avoiding it for as much as I can (it's sad that it starts being like a requirement at work), and if I'm ever going to use it it'll be for small, boring tasks, not for anything big that would leave a lot of junk food on the table. My trust is so low that I refrain from personally trying projects that seem genuinely useful, like this one (entirely vibe-coded). I hope it won't invade much open source software that I use.

[ By the way, did you notice how buggy Github is lately? The start of the troubles seems to coincide with the advent of AI.. just sayin'. ]

Don't become a full-slop developer.

Footnotes
1. A secondary reason: Claude, for example, is owned by a corporation which only cares about one thing — returning a profit to their shareholders, who have already burned billions. If it's tuned for anything, like corporations always do, it's tuned for their profit, and this, believe it or not, is at odds with Claude working great for you. When competition is eliminated, the only way to extort more money is to make the product worse (and/or increase prices for the same functionality). Enshittification always happens with any VC funded company that gets big enough.
One comment. ONE! Gimme some more!

Add your comment

# RevAaron
2026-08-05 01:09
I don't think the analogy is wrong at all. But I'd like to share the analogy I've been thinking about myself the last few days. For me, vibe coding is basically the ideal video game. One of the "vibe coding video games" I've been playing lately is having AI re-implement scripts I use every day in different programming languages. I wrote a simple version control system called arx that I use daily to manage a directory of scripts and config files, like ~/bin, on a lot of different isolated nodes. Arx isn't huge (1300 lines of python) but it's non-trivial. It's code I understand well - which makes it a great way to learn other languages and framework. The quick back and forth, elaborating, chasing the dopamine hit of a fixed bug that you didn't fix yourself - it feels a lot like video games, junk food, or nicotine. Don't get me wrong, I understand the arguments against it... But hell, it can be so much fun. The other value vibe coding has added to my life is that it's allowed me to implement tools and integrations I wouldn't have the time to do otherwise. I've got a long wish list of tool ideas I've come with over the years, some of them a decade old. Most of these tools are so specific to my requirements that the potential audience for them is probably a dozen people throughout the world who use the same proprietary db/tool and workflow like my own. As much as I'd like to spend my days writing those programs, I have to pick my battles if I want to get my actual job done. My day job is managing some of the most critical systems at utility company, and I'm alarmed at the idea of our core application vendors introducing vibe coded nonsense that they don't understand. Hell, it already feels like our main vendor's current roster of employees doesn't understand the system and how it works, and that's even before any of it's been vibe coded. I think you'd be insane to build large enterprise systems on thousands of lines of code that your engineers haven't even actually vetting. Maybe they've pretended to, maybe they did at first - but at some point, they likely stopped and just perform functional tests. That scares me.
Jul
1
2026

Vibe-coded software is junk food

  • Published: 2026-07-01
  • Modified: 2026-07-01 21:52
  • By: Mishoo
  • Tags: ai, vibe-coding
  • Comments: 1 (add)