“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 found that it only does well if the task is already well covered by the usual sources. Ask for anything novel and it shits the bed.
That’s because it doesn’t understand anything and is just vomiting forth output based on the code that was fed into it.