This is why you should not install any of the vibe coded apps that get advertised in here regularly. You’re just creating a liability for yourself.
This is why you should not install any of the vibe coded apps that get advertised in here regularly. You’re just creating a liability for yourself.
It’s late and so maybe I missed it, but I didn’t see the part of the article that compares the abandon rate of slopcode with the overall abandon rate. Not saying that the premise is wrong or anything, but you can’t tell how bad something is unless you can compare it with the norm.
I would guess that the key difference is that vibe coded apps can get to a more or less working state a lot quicker, while other apps are likely to be abandoned before it’s done.
Though in either case I’d always be careful with new projects. If it’s just a single guy that’s been working on something for less than a year and only have a handful of GitHub stars, I probably wouldn’t install it.
Also it’s again the false sense of security pf “if you don’t use vibed apps you’ll be fine”, making people forget basic security procedures.
I, for instance, had a service vulnerable and discontinued without noticing for months. It was something 100% made before LLM was a thing. Still had unpatched vulnerabilities and the project was abandoned. It was my fault for not checking more often is the services I host are safe or not.
I’ve been working on updating all my old software projects lately, and as part of that process I feed the source code into a LLM for review.
The amount of simple security errors, logic flaws, and code smells that it reveals is quite embarrassing.
This was all “good functional code” that’s been used internally for years. Clearly it worked well enough, but a simple pass through a LLM reviewer made it a lot more robust and secure.