Vibe coding is asking gpt for code, copying it into your code environment, then telling gpt about any errors or issues. The problem is that it actually works a significant amount of the time, let’s be generous and say 80%. Another 15% of the time it cannot solve a problem itself. And finally the worst possible outcome is the last 5%, where it creates a seemingly working solution that actually breaks on edge cases or has potential security issues.
Comment on Vibe coding has turned senior devs into ‘AI babysitters,’ but they say it’s worth it | TechCrunch
CaptainBlinky@lemmy.myserv.one 3 weeks ago
I keep seeing “vibe coding.” WTF is vibe coding? ELI5
PlantJam@lemmy.world 3 weeks ago
ngcbassman@sh.itjust.works 3 weeks ago
One important aspect of vibe coding that I always see that is missing in explanatuons is that is the generation of code through AI, but without understanding what the code is doing, the effect of this is you are totally dependant on the AI to keep generating the code, so if any error happens you don’t have fucking idea in what to do. If you generate the code using AI and you understood what the AI did, is not vibe coding.
NocturnalEngineer@lemmy.world 3 weeks ago
A security nightmare waiting to happen.
sugar_in_your_tea@sh.itjust.works 3 weeks ago
Also performance, maintenance, and regression.