this is the one and only reason that the Linux kernel is going out of its way to hide which commits are LLM generated by abolishing the Assisted-By tag, simultaneously with torvalds fully slopcoding a core “improvement” to the kernel’s memory management

if you don’t believe me, here’s part of what the diff removed from the kernel’s docs:

> -When AI tools contribute to kernel development, proper attribution
> -helps track the evolving role of AI in the development process.
> -Contributions should include an Assisted-by tag in the following format::

and surprise, here’s the dickheads responsible: en.wikipedia.org/wiki/Linux_Ke a set of people who get money and tokens from Anthropic, OpenAI, and a bunch of other AI corps via the Linux Foundation

don’t you love when the paid heads of a community project meet behind closed doors to do something that damages the community? furs.social/@Rycochet/11743896

en.wikipedia.org/wiki/Linux_Kernel_Developers_Summit

Replying to @⁨zzt@mas.to⁩

I’m pushing this reply to top level because it’s extremely important: is.badat.dev/objects/a142a17d-

> I asked whether that risked cutting off bright new developers that we would rather hang onto; Torvalds answered that the kernel project only wants serious developers. That includes having access to enough resources to function in this world.
> [...]
> Torvalds added that he does not want to scare off people who want to write code; his message is that you have to either put in the effort to learn, or put a lot of money into an LLM to participate.

Linus Torvalds prefers if you can’t contribute to the kernel without pouring money into tokens for Claude Code

if you don’t pay a shit ton of money for tokens, you aren’t a serious developer according to him

the “learn” thing here is a distraction: in this context, you’ll be learning to clean up slop until you either burn out (very quickly at that) or pay for tokens and cognitively surrender to the bot

that’s the learning path now

is.badat.dev/objects/a142a17d-9320-4007-bef4-99762f9fa854

Replying to @⁨zzt@mas.to⁩

@zzt

This paragraph just gets better every sentence.

> He has been playing with an LLM on a separate project for several months to learn about the technology, but hadn't used one on the kernel until last week. He took an old patch and had the LLM revise it; the result has made him unwilling to work without an LLM. He plans to post that series at some point. Why bother, he asked, to search for all of the call sites of a function he has just modified, when the tool can fix them all automatically? But, he said, it took six months to set up the tool to not produce bad responses. If you are a competent developer, he said, an LLM makes a great tool, but only after that effort has been put in to set it up. He resisted suggestions to post his LLM-training materials, saying that each developer needs to go through that process separately.

en