Comment on Most slopcode projects are abandoned and deleted within months of release
Flames5123@sh.itjust.works 6 days agoI 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.
dan@upvote.au 6 days ago
The major issue I’m seeing with junior developers at work is that they trust that the AI will always do things the correct way, and don’t question its approach.
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.
MirrorGiraffe@piefed.social 6 days ago
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.
searabbit@piefed.social 6 days ago
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.
kevin2107@lemmy.world 6 days ago
I’m in some deep shit because my manager put colleague in charge of a project and he chose to slopcode a solution I don’t understand. Now our client wants to understand it and the code is absolute shit. His only solutions are “did you ask Claude”