- cross-posted to:
- programming@programming.dev
- cross-posted to:
- programming@programming.dev
“No Duh,” say senior developers everywhere.
The article explains that vibe code often is close, but not quite, functional, requiring developers to go in and find where the problems are - resulting in a net slowdown of development rather than productivity gains.
Oddly enough, my grasp of coding is probably the same as the guy in the middle but I still know that LLM generated code is garbage.
Yeah, I actually considered putting the same text on all 3, but we gotta put the idiots that think it’s great somewhere! Maybe I should have put it with the dumbest guy instead.
Think this one needs a bimodal curve with the two peaks representing the “caught up in the hype” average coder and the realistic average coder.
Agreed, that’s why it didn’t feel quite right when I made it.
Yeah, there’s definitely morons out there who never bothered to even read about the theory of good code design.
I guess I’m one of the idiots then, but what do I know. I’ve only been coding since the 90s
All the best garbage to learn from, to debug, debug, debug, sharpening those skills.
That’s kinda wrong though. I’ve seen llm’s write pretty good code, in some cases even doing something clever I hadn’t thought of.
You should treat it as any junior though, and read the code changes and give feedback if needed.