“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 thought that as well and got some code from someone that left the company and asked it to comment it.
It did the obvious “x= 5 // assign 5 to x” crap comments and then it got to the actually confusing part and just skipped that mess entirely…