What is the sentiment of vibe coded crates?

[ajmull]

@MOCKBA

It's written in .ts, and I do not understand it, but how the code organized and how it works, I can conclude that it's perfect.

What if something goes wrong? What if you find a bug that you never saw before? "Just ask the LLM to fix it," you might say. That simply makes the situation worse. I can't write this without sounding like @khimru, so here is what they said:

@khimru

I'm, honestly, impressed by LLMs tenacity and they ability to add… kludgy solutions to the reported issues and contain the code in some kind of half-working state… most humans would cry out it's not possible to support that, but models add kludges on top of kludges… but at some point the whole thing collapses, anyway — and by then it's too convoluted for anyone to fix.

@MOCKBA

vibe coded code is much better than they [(beginner-level programmers)] programmed themselves.

People become programmers for two reasons:

• The jobs/money.
• They enjoy programming and learning about it.

Generally a mix of both.
The first point is obsolete now, leaving us with programmers who code because they love it. This is the best kind of programmer. Now, sure, a plagiarising algorithm might be better than a new coder, but why would they outsource their passion? Why would anyone let a machine do what they love for them? It takes all the joy out of programming.

Yet another huge issue with AI is that it removes the maintainer. It removes the person who knows the code and how it works. When it all goes to pot, who does the user tell? You're not in charge. You didn't make the code. You don't even have a clue how it works!

@ajmull

Looking at a piece of vibe-code, trying to debug it, is like looking at someone else's work: foreign, unknown, and you don't know where to start. People who maintain applications will be no better at eliminating issues within it than someone who found the issue in the first place.