Programming

22950 readers

39 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

UlrikHD@programming.dev

262

AI Coding Is Massively Overhyped, Report Finds (futurism.com)

submitted 3 days ago* (last edited 3 days ago) by HaraldvonBlauzahn@feddit.org to c/programming@programming.dev

42 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] HaraldvonBlauzahn@feddit.org 6 points 2 days ago (2 children)

I always wondered how they got those original productivity claims.

Probably by counting produced lines of code, regardless their correctness or maintainability.

And that's probably combined with what John Ousterhout calls "Debugging a System into Existence", which is, just assuming the newly generated code works until inevitably somebody comes with a bug report and then doing the absolute minimum to make that specific bug report go away, preferably by adding even more code.

[–] droans@midwest.social 2 points 2 days ago

It seems like a good way to actually determine productivity would be to make it competitive.

Have marathon and long-term coding competitions between 100% human coding, AI assisted, and 100% AI. Rate them on total time worked, mistakes, coverage, maintainability, extensibility, etc. and test the programmers for knowledge of their own code.

[–] dumples@midwest.social 1 points 2 days ago

That what I thought. Each line of generated code even if deleted afterwards. Or have someone try to get as high as possible in a single trial