"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.

you are viewing a single comment's thread
view the rest of the comments
[–] 11 points 1 year ago*

That's because it doesn't understand anything and is just vomiting forth output based on the code that was fed into it.

  • source
  • parent