The AI industry's claims about AI coding assistants boosting productivity significantly appear to be massively overblown, per a new report.

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

  • MangoCats@feddit.itEnglish
    32·
    19 hours ago

    (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?

    • Warl0k3@lemmy.worldEnglish
      31·
      18 hours ago

      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.

      • MangoCats@feddit.itEnglish
        3·
        18 hours 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.