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

With an understanding of good practice, a proper development environment and a close eye on the junior devs, there’s no inherent issue to using it.

My feelings about C/C++ are the same. I'm still switching to Rust, because that's what the company wants.

  • source
  • parent