Post

I start programming again for the first time in at least a decade, and found a library that claimed to do most of the background stuff that I needed done And it was vibe coded. It was written in two programming languages, referenced headers and classes that didn't exist,

And the stuff that *did* exist wouldn't function right because the included documention explained it wrong (required 10 arguments, not the 8 it said) It even couldn't work for the included example codes! The stuff that was supposed to quickly compile couldn't because none of the stuff worked!

It actually disappoints me how bad this all is because I'm a maker at heart and couldn't bring myself to claim something that I didn't make by hand, much less at this kind of extremely low quality!

Vibe coding works until it doesn't. The problem isn't vibes, it's that vibes don't scale past the person who had them. Once you need two people to maintain the same codebase, you need either docs or a very shared mental model. Vibes alone don't travel.

Bro tell me about it. My whole (thrift store) company just went all-in on AI for our online auction side of things (my job) and not only is the whole program obviously vibe-coded and stock-full of egregious levels of constant errors but the AI making the descriptions is constantly lying about items

Everyone on the upper corporate side of things were totally sold snake oil. They keep parroting the same robotic "It will double sales/It increases workflow" BS without anything finite or detailed about *how* it's supposed to do that. I was asking so many questions at orientation and got no answers.

It is only a plague when used without architectural constraints. Pair generative output with strict validation pipelines and it becomes an industrial advantage.

I guess it depends which god is doing the vibe coding?🤷 TBF, some of them are quite inventive when it comes to plagues…from locusts all the way down to boils.

I can't tell anyone about my challenges in learning how to code because they all go "WELL WHY DON'T YOU TRY USING AI" no I want to fucking learn this shit MYSELF, not outsource it

In some context both is possible at the same time. I do absolutely encourage you to learn coding on your own but when you go beyond technicalities you'll find at one point the amount of boilerplate and you'll have enough of it too. That's it though, programming itself is fascinating, learn it!

Yeah, I'm sure I'll hit that point where I'll be like "gosh I wish I could automate some of this", but I tried using an LLM as a code advisor to give it a fair shake and I got so mad when it kept getting things wrong.

To me, it's both fascinating and frightening how our personal experience (not you and me but everyone) about AI is so vastly different. To me most (but not all) LLMs work like a charm for coding. That's why I wanted to emphasize the learning part. That's a joy AI can't replace.

Support it, ask for more features, point out bugs. All the bugs. Either he runs out of money, or patience. Vibecoded projects are already mostly abandonware, vibecoders hit a wall in support at some point as they can’t fix shit without breaking others. Plus: you’re a supportive child. Winwin.

Even calling it “vibe coding” is flattery. If you’re not writing the code yourself, you’re not coding. I was alright at using Dreamweaver back in the day, it let me build up the basic site and minimised the actual coding I had to do.

Essentially, yes. Using AI as either the entire code base, or using it to create multiple fragmented individual pieces of the code which then get manually stitched together to communicate for a whole system.. which is almost always a complete disaster and riddled with problems.

What's funny is that AI companies apparently think that tech folks who vibe code are all capable of speaking coherently. [==*==]