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.
Vibe coding a simple project is easy, but a crapshoot, at the current state of LLM development. Vibe maintaining anything at all is basically impossibly currently, you need a competent developer for that.
I agree that people cannot vibe code well unless they are a developer. Knowing the difference between slop and using a tool to automate bulk writing code is crucial at the current state. And I don’t ever know if it’ll get better because you need to know why you want to build something someway.
The major issue I’m seeing with junior (and even intermediate) developers is that they trust that the AI will always do things the correct way and don’t question its approach, and they don’t develop proper debugging skills and just rely on the AI to attempt it.
To get decent quality output out of an AI model, you need to have critical thinking skills, at least basic knowledge of the overall architecture for whatever you’re trying to build, and enough knowledge to question the model when it does something wrong.
Blindly trusting AI is why so many old security issues are coming back - stored/reflected XSS, SQL injection, exposing databases directly to the internet with no password, things like that. Newer frameworks mostly got rid of them, and now AI is bringing them back. It’s a fun time for red teams at least.
As someone somewhere between junior and intermediate developer, I will say vibe coding on my personal projects has accelerated my learning so much on the proper way to code things so much more than constantly bugging my seniors who don’t have time to properly review and critique my code (because surprise surprise! We’re understaffed). At least now I can ask Claude to explain its approach and fact check it myself, and the times I’ve had it run too loose, I’ve gotten practice debugging code I’m unfamiliar with since Claude eventually hits a point where it fucked something up and has no idea how to fix it. But obviously the caveat is you have to approach it as a learning tool not an automation tool.
I’m a developer since 20 years and been trying out vibing godot and I expected it to have troubles with Godot but at least getting basic programming paradigms right but it has been more the other way around. I’m constantly policing it for hardcoding or creating unmaintainable messes where the base classes have exceptions for each child instead of them owning their own logic.
Disagree. It’s perfectly viable. I’ve maintained several projects for over a year myself
Are you maintaining them for your own use, or do they have other users who you are supporting?
I have a few projects, some are just for me. And others are available for use. Mostly plugins for other projects, couple hundred people using them.
They all have good cocd pipelines with testing, code validation/ static code analysers. It’s trivial to maintain. Not big projects by any means but 20-50k loc
Can you name the one with the largest user base? How do you distribute it? What’s the ecosystem?
Are these projects… in the room with us right now?
I’m not the one throwing out baseless accusations
Just baseless claims.
I have nothing to prove
That is you making a claim.
That is you trying to prove said claim with anecdotal evidence. If you had nothing to prove, you’d have made the right choice and stfu.
Then why would anyone believe what you said?
Why would they believe the other guy?
Sounds interesting.
Can you link those projects please?
Oh here we go