cross-posted from: https://lemmy.zip/post/49954591

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

Then there’s the issue of finding an agreed-upon way of tracking productivity gains, a glaring omission given the billions of dollars being invested in AI.

To Bain & Company, companies will need to fully commit themselves to realize the gains they’ve been promised.

“Fully commit” to see the light? That… sounds more like a kind of religion, not like critical or even rational thinking.

  • kidney_stone@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    4 months ago

    I have to say that I am surprised by how many people are bashing on AI coding.

    I personally use AI tools like cursor and claude code to help me with code, and I have to say that they are incredibly helpful with managing huge codebases and fixing repetitive elements. Obviously, I have to know a lot about coding and system design and whatnot, and I have to write many instructions, so it can’t ‘replace programmers’ or anything. But in the hands of those who already know their stuff, it really does speed things up significantly.

    I have no idea how other people are using it that is inspiring all these reports on how awful AI coding is. Do non-programmers just enter Claude and write “make program!!!” and then expect it to work?