“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.
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.
I guess I’m one of the idiots then, but what do I know. I’ve only been coding since the 90s
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.