pull down to refresh
Yes, but even if they aren't it's cognitive debt from a maintainer perspective if you don't understand everything it does. The advice many of the vibe kings give you is to just accept everything and let the LLM solve everything, including bugs it coded itself.
That means you know nothing, and you'll be happy, until it nips you in the butt with a bug it gets stuck on, and then you're fucked, because now you have to go through 100k lines of slop and try to make sense of it (which is really, really hard.)
Like a ticking time bomb. I was really surprised by this. I thought these "devs" at least somewhat kept up with the AI's work. Now that I know they don't read, just like people who ask you to summarize an email and don't read it, I've completely lost respect. One more checkpoint for when I use someone's project:
- FOSS (check)
- No Vibe Code (check)
What could work though is that you take some vibe coded thing and you let an LLM code something up for you based on it. Don't publish the resulting product, because you don't want to be held liable (not even legally; reputationally) for stuff you don't understand. Just use it to your own advantage.
Is it true that these vibe codes are full of crap that can become a problem to manage and maintain throughout the code's lifespan?