“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 think maybe a good comparison is to written papers/ assignments. It can generate those just like it can generate code.
But it is not about the words themself, but about the content.