this post was submitted on 17 Aug 2026
88 points (90.7% liked)

Technology

87183 readers
3870 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 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] it_depends_man@lemmy.world 2 points 5 hours ago (3 children)

Torvalds was careful to frame this as a correction of language rather than a rejection of the technology itself.

Ok...

A maintainer burden few are talking about

Alongside the productivity gains, Torvalds described a less-discussed cost: a rising flood of low-effort, AI-generated bug and vulnerability reports hitting open source projects, including the kernel’s own security channels. He said it has become common for someone to run an AI tool against a codebase, file a report flagging a “possible” issue, and then vanish when a maintainer follows up asking for more detail or a fix.

Everyone is talking about that and it is surprising to me that he doesn't recognize that as two side of the same coin. Why are you rejecting the low-effort, Ai generated bug reports, Linus, isn't AI just a productivity tool? What's wrong? Is it not being productive?

I say "surprising", it's not that surprising. It's a "guns don't kill people, people kill people" attitude. It's willfully excluding the impact that technology has on people, and framing the outcome as coming purely from people and the existence of the technology not affecting the outcome.

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

Why are you rejecting the low-effort, Ai generated bug reports, Linus, isn't AI just a productivity tool?

Because they are low effort. Good software engineering is never low effort, whether you use AI or not.

If you let AI replace people, and let them mess with software or report issues without understanding what's going on, without putting in the effort to understand what's going on, you're not adding any value; just noise.

But if you use AI to find issues, then investigate the issue, reproduce it, document it, etc, then you've got something meaningful that someone can do something with.

[–] MalReynolds@slrpnk.net 1 points 2 minutes ago

But if you use AI to find issues, then investigate the issue, reproduce it, document it, etc, then you’ve got something meaningful that someone can do something with.

In principle that is sound, but LLMs can't do that, yet, if ever. Sounds like anthropomorphism. The 'hallucination' thing is intrinsic. What you can do is point it at easily verifiable problems like searching for security flaws, and then verify them. Whether that's cost effective in wasted energy and human time is still an open question, especially as token cost ramps up pre IPO.

[–] douglasg14b@lemmy.world 24 points 5 hours ago (1 children)

.... What?

Lazy people using tools in a shitty manner has been an age old problem.

This just lets it scale, which is the problem. There used to be a barrier to entry for those less knowledgeable or experienced, now there isn't and that's the result.

It is a productivity tool, and it's being used as one, by both people that know how and people who don't.

[–] rozodru@piefed.world 2 points 1 hour ago

bingo. and unfortunately the lazy and inexperienced are using it more than others, or using it at a much higher degree. Linus even says it himself. they file a report and then "vanish" because they can't answer follow up questions or clarifications because they don't know how. if you deal with LLMs and the people that use them as much as I do for my job you see this constantly. daily even. they "build" something and when it's reviewed and questioned the answers are just no where to be found because the "coder" can't answer them.

Like the other day there's this guy on Youtube who is a huge advocate for Omarchy for whatever reason. older guy but he's always going on about how great Omarchy is. he posts a video about how "we" built some application for Omarchy but the entire video is him putting prompts into Claude Code and then walking away. never touches it, never writes a line of code. but there were glaring bugs with the build so I reached out to him, asked him how he was going to address these things and hoping he wouldn't put this app out there because it's clearly broken. works on a surface level but it WILL break. he essentially told me to "fuck off".

you're right an LLM is a tool but one that should be in the hands of those that know what they're doing. you wouldn't hand a hammer to a child and tell them to build a house. you wouldn't hand a gun to a junkie and tell them they're now a cop. I wouldn't hand Vim to my mother and tell her to build a website. I feel LLMs should require human training just like any other tools we use. If you want to allow LLMs into your open source project, sure, have at it but it should be YOUR responsibility to vet and interview each individual that wishes to contribute utilizing said tools.

[–] ImgurRefugee114@reddthat.com 31 points 5 hours ago* (last edited 5 hours ago) (2 children)

Tools are just tools; there are good ways and bad ways to use them. "Grok, go find bugs in the Linux kernel" isn't a good one. This isn't hard to understand...

There were many, partially well-intentioned, mostly fame-seeking, one-off 'projects' 'scanning' public repos and flooding them with low-quality low-effort PRs and issues; things that no human ever read until the a maintainer did.

"They made a poison and sold us a cure" is absolutely a valid criticism; that's two sides of the same coin. But pretending that he's being hypocritical or that LLMs aren't useful is just being wrong for the sake of hating AI

AI is useful as tool like he said, unfortunately these days in many organisations it is used as a replacement rather than a tool.

His conclusion was that as AI tools get more capable, the people who actually understand how systems work become more valuable, not less — because someone still has to review, maintain, and take responsibility for what the tools produce.

Humans still need to learn how to code.

[–] it_depends_man@lemmy.world 2 points 4 hours ago

Tools are just tools

I don't think that's true, but we simply disagree on that.

I don't think he's hypocritical. He simply doesn't have to deal with that negative impact he "warns" about. He is in support of using it as a tool and thinks the criticism is invalid. That's a consistent perspective, even if I don't agree with it.

If he used LLMs to create bug reports, but also complained about LLM written bug reports he gets, that would be hypocritical.