"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
[–] 2 points 1 year ago

It's not bad for your use case but going beyond that without issues and actual developpers to fix the vibe code is not yet possible for llms

  • source
  • parent