"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
[–] 1 point 1 year ago (2 children)

(asking GPT-5 to do your dynamic SQL calls is inviting disaster, for example. Requires hours of reworking just to get close.)

Maybe it's the dynamic SQL calls themselves that are inviting disaster?

  • source
  • parent
  • hideshow 2 child comments
  • [–] 3 points 1 year ago* (1 child)

    Dynamic SQL in of itself not an issue, but the consequences (exacerbated by SQL's inherent irrecoverability from mistakes - hope you have backups) have stigmatized its use heavily. 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.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 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