- 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.
I can’t even get Copilot to write Vitest files for React without making a mountain of junk code that describes drivel.
Were you trying to say “drivel?”
Yes. I’ll go fix that.