“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.
This. Like with any tool you have to learn how and when to use it. I’ve started to get the hang of what tasks it improves but I don’t think I’ve regained the hours I’ve spent learning it yet.
But as the tool and my understanding of it improves it’ll probably happen some day.