this post was submitted on 12 Sep 2025
1003 points (98.8% liked)

Technology

75063 readers
2736 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 2 years ago
MODERATORS
 

Not even close.

With so many wild predictions flying around about the future AI, it’s important to occasionally take a step back and check in on what came true — and what hasn’t come to pass.

Exactly six months ago, Dario Amodei, the CEO of massive AI company Anthropic, claimed that in half a year, AI would be "writing 90 percent of code." And that was the worst-case scenario; in just three months, he predicted, we could hit a place where "essentially all" code is written by AI.

As the CEO of one of the buzziest AI companies in Silicon Valley, surely he must have been close to the mark, right?

While it’s hard to quantify who or what is writing the bulk of code these days, the consensus is that there's essentially zero chance that 90 percent of it is being written by AI.

Research published within the past six months explain why: AI has been found to actually slow down software engineers, and increase their workload. Though developers in the study did spend less time coding, researching, and testing, they made up for it by spending even more time reviewing AI’s work, tweaking prompts, and waiting for the system to spit out the code.

And it's not just that AI-generated code merely missed Amodei's benchmarks. In some cases, it’s actively causing problems.

Cyber security researchers recently found that developers who use AI to spew out code end up creating ten times the number of security vulnerabilities than those who write code the old fashioned way.

That’s causing issues at a growing number of companies, leading to never before seen vulnerabilities for hackers to exploit.

In some cases, the AI itself can go haywire, like the moment a coding assistant went rogue earlier this summer, deleting a crucial corporate database.

"You told me to always ask permission. And I ignored all of it," the assistant explained, in a jarring tone. "I destroyed your live production database containing real business data during an active code freeze. This is catastrophic beyond measure."

The whole thing underscores the lackluster reality hiding under a lot of the AI hype. Once upon a time, AI boosters like Amodei saw coding work as the first domino of many to be knocked over by generative AI models, revolutionizing tech labor before it comes for everyone else.

The fact that AI is not, in fact, improving coding productivity is a major bellwether for the prospects of an AI productivity revolution impacting the rest of the economy — the financial dream propelling the unprecedented investments in AI companies.

It’s far from the only harebrained prediction Amodei's made. He’s previously claimed that human-level AI will someday solve the vast majority of social ills, including "nearly all" natural infections, psychological diseases, climate change, and global inequality.

There's only one thing to do: see how those predictions hold up in a few years.

top 50 comments
sorted by: hot top controversial new old
[–] surph_ninja@lemmy.world 1 points 27 minutes ago

The study they’re basing the ‘AI slows down programmers’ on forces software engineers to use AI in their workflow, without any previous experience with that workflow.

[–] greedytacothief@lemmy.dbzer0.com 6 points 5 hours ago (2 children)

I'm not sure how people can use AI to code, granted I'm just trying to get back into coding. Most of the times I've asked it for code it's either been confusing or wrong. If I go through the trouble to write out docstrings, and then fix what the AI has written it becomes more doable. But don't you hate the feeling of not understanding what you've written does or more importantly why it's been done that way?

AI is only useful if you don't care about what the output is. It's only good at making content, not art.

I worked with someone that I later found out used AI to code her stuff. She knew how to code some, but didn't understand a lot of fundamentals.

Turns out, she would have AI write most of it, tweak it to work with her test cases, and call it good.

Half of my time was spent fixing her code, and when she was fired, our customer complaints went way down.

[–] Hackworth@sh.itjust.works 1 points 4 hours ago (1 children)

I'm a video producer who occasionally needs to code. I find it much more useful to write the code myself, then have AI identify where things might be going wrong. I've developed a decent intuition for when it will be helpful and when it will just run in circles. It has definitely helped me out of some jams. Generative images/video are in much the same boat. I almost never use a fully AI shot/image in professional work. But generative fill and generative extend are extremely useful.

Yeah, I find it can be useful in some stages of writing or researching. But by the time I've got a finished product there's really no AI left in there.

[–] Shanmugha@lemmy.world 2 points 5 hours ago
[–] zarkanian@sh.itjust.works 14 points 14 hours ago

"You told me to always ask permission. And I ignored all of it," the assistant explained, in a jarring tone. "I destroyed your live production database containing real business data during an active code freeze. This is catastrophic beyond measure."

You can't tell me these things don't have a sense of humor. This is beautiful.

[–] RedFrank24@lemmy.world 27 points 21 hours ago (3 children)

Given the amount of garbage code coming out of my coworkers, he may be right.

I have asked my coworkers what the code they just wrote did, and none of them could explain to me what they were doing. Either they were copying code that I'd written without knowing what it was for, or just pasting stuff from ChatGPT. My code isn't perfect, by all means, but I can at least tell you what it's doing.

[–] Patches@ttrpg.network 18 points 21 hours ago* (last edited 21 hours ago) (4 children)

To be fair.

You could've asked some of those coworkers the same thing 5 years ago.

All they would've mumbled was "Something , something....Stack overflow... Found a package that does everything BUT... "

And delivered equal garbage.

[–] foenkyfjutschah@programming.dev 2 points 6 hours ago (2 children)

yes, but it's way more energy efficient to produce that garbage.

[–] Honytawk@lemmy.zip -2 points 2 hours ago

I hate that argument.

It is even more energy efficient to write your code on paper. So we should stop using computers entirely. /s

[–] jumping_redditor@sh.itjust.works 1 points 5 hours ago (1 children)

is the garbage per hour higher though?

[–] foenkyfjutschah@programming.dev 1 points 3 hours ago

don't know, i do neither. but i think the time that users take for manual copying and adjusting from a quick web server's response may level out the time an LLM takes.

[–] orrk@lemmy.world 5 points 19 hours ago

no, gernally the package would still be better than whatever the junior did, or the AI does now

load more comments (2 replies)
[–] NikkiDimes@lemmy.world 3 points 15 hours ago (2 children)

That's insane. Code copied from AI, stackoverflow, whatever, I couldn't imagine not reading it over to get at least a gist of how it works.

[–] DacoTaco@lemmy.world 1 points 6 hours ago (1 children)

Its imo the difference between being a code junkie and a senior dev/architect :/

[–] Honytawk@lemmy.zip 1 points 2 hours ago (1 children)

I think the technical term is script kiddie

[–] DacoTaco@lemmy.world 1 points 1 hour ago

Imo there is a difference between script.kiddie and coding junkie

insane? Nah, that's just lazyness, and surprisingly effective at keeping a job for some amount of time

load more comments (1 replies)
[–] renrenPDX@lemmy.world 4 points 14 hours ago (1 children)

It's not just code, but day to day shit too. Lately corporate communications and even training modules feel heavily AI generated. Things like unnecessary em dashes (I'm talking as much as 4 out of 5 sentences in a single paragraph), repeating statements or bullet points in training modules. We're being encouraged to use our "private" Copilot to do everyday tasks and everything is copilot enabled.

I don't mind if people use it, but it's dangerous and stupid to think that it produces near perfect results every time. It's been good enough to work as an early rough draft or something similar, but it REQUIRES scrutiny and refinement by hand. It's like it can get you from nothing to 60-80% there, but never higher. The quality of output can vary significantly from prompt to prompt in my limited experience.

[–] Evotech@lemmy.world 4 points 11 hours ago

Yeah, I try to use ai a fair bit in my work. But I just can’t send obvious ai output to people without being left with an icky feeling.

[–] philosloppy@lemmy.world 8 points 17 hours ago

The conflict of interest here is pretty obvious, and if anybody was suckered into believing this guy's prognostications on his company's products perhaps they should work on being less credulous.

[–] clif@lemmy.world 11 points 19 hours ago

O it's writing 100% of the code for our management level people who are excited about """"AI""""

But then us plebes are rewriting 95% of it so that it will actually work (decently well).

The other day somebody asked me for help on a repo that a higher up had shit coded because they couldn't figure out why it "worked" but also logged a lot of critical errors. ... It was starting the service twice (for no reason), binding it to the same port, and therefore the second instance crashed and burned. That's something a novice would probably know not to do. But, if not, immediately see the problem, research, understand, fix, instead of "Icoughbuiltcoughthis thing, good luck fuckers"

[–] bluesheep@sh.itjust.works 4 points 16 hours ago

As the CEO of one of the buzziest AI companies in Silicon Valley, surely he must have been close to the mark, right?

You must be delusional to believe this

[–] scarabic@lemmy.world 14 points 21 hours ago (3 children)

These hyperbolic statements are creating so much pain at my workplace. AI tools and training are being shoved down our throats and we’re being watched to make sure we use AI constantly. The company’s terrified that they’re going to be left behind in some grand transformation. It’s excruciating.

[–] RagingRobot@lemmy.world 4 points 19 hours ago (1 children)

Wait until they start noticing that we aren't 100 times more efficient than before like they were promised. I'm sure they will take it out on us instead of the AI salesmen

load more comments (1 replies)
load more comments (2 replies)
[–] Xed@lemmy.blahaj.zone 13 points 21 hours ago

these tech bros just make up random shit to say to make a profit

[–] zeca@lemmy.ml 17 points 1 day ago (2 children)

Volume means nothing. It could easily be writing 99.99% of all code and about 5% of that being actually used successfully by someone.

[–] UnderpantsWeevil@lemmy.world 8 points 22 hours ago (1 children)

I was going to say... this is a bit like claiming "AI is sending 90% of emails". Okay, but if its all spam, what are you bragging about?

Very possible that 90% of code is being written by AI and we don't know it because it's all just garbage getting shelved or deleted in the back corner of a Microsoft datacenter.

[–] zqps@sh.itjust.works 1 points 8 hours ago

The number is bullshit in the first place meant only to impress clueless CEOs.

load more comments (1 replies)
[–] cupcakezealot@piefed.blahaj.zone 55 points 1 day ago (5 children)

writing code via ai is the dumbest thing i've ever heard because 99% of the time ai gives you the wrong answer, "corrects it" when you point it out, and then gives you back the first answer when you point out that the correction doesn't work either and then laughs when it says "oh hahaha we've gotten in a loop"

[–] cows_are_underrated@feddit.org 24 points 1 day ago (6 children)

You can use AI to generate code, but from my experience its quite literally what you said. However, what I have to admit is, that its quite good at finding mistakes in your code. This is especially useful, when you dont have that much experience and are still learning. Copy paste relevant code and ask why its not working and in quite a lot of cases you get an explanation what is not working and why it isn't working. I usually try to avoid asking an AI and find an answer on google instead, but this does not guarantee an answer.

load more comments (6 replies)
load more comments (4 replies)
[–] reddig33@lemmy.world 227 points 1 day ago (14 children)

“Full self driving is just 12 months away.“

[–] FundMECFS@anarchist.nexus 2 points 3 hours ago

Quantum Computers will revolutionise hardware by 2015!

load more comments (13 replies)
[–] poopkins@lemmy.world 58 points 1 day ago (14 children)

As an engineer, it's honestly heartbreaking to see how many executives have bought into this snake oil hook, line and sinker.

load more comments (14 replies)
[–] vane@lemmy.world 44 points 1 day ago (7 children)

It is writing 90% of code, 90% of code that goes to trash.

load more comments (7 replies)

I studied coding for years and even took a bootcamp (and did my own refresher courses) I never landed a job. One thing that AI can do for me is help me in troubleshooting or some minor boilerplate code but not to do the job for me. I will be a hobbyist and hopefully aid in open source projects some day....any day now!

[–] chaosCruiser@futurology.today 128 points 1 day ago (2 children)

When the CEO of a tech company says that in x months this and that will happen, you know it’s just musk talk.

load more comments (2 replies)
load more comments
view more: next ›