cross-posted from: https://piefed.social/c/linux@programming.dev/p/2509642/linus-torvalds-posts-his-first-ai-assisted-patch-to-the-linux-kernel-synthetic-test-clo
What gets me is that this is roughly the best-case scenario for “capable hands” — Linus knows this codebase better than anyone alive — and a race condition plus a 9% read regression still slipped through on the first attempt. Reviews and testing caught it, which is the system working, but it moves the bottleneck from writing code to reviewing it. And review doesn’t scale the way generation does; skimming a patch is quick, but actually proving an LLM-assisted one is correct takes real effort. I say that as someone who uses AI tooling daily — reading code you didn’t write is genuinely more tiring than writing it, and that tax compounds the more you lean on generation. The maintainer-burnout angle might end up being the real story here, more than the AI one.
reading code you didn’t write is genuinely more tiring than writing it
What I keep saying. Good take except that you don’t use “AI” tooling, you use copyright evasion slop tooling.
I thought code couldn’t be copywritten? It’s instructions, isn’t it?
Instructions can be copywritten just like recipes can.
Code is just a recipe for computer brains
Half a century of companies suing each other over code licenses suggests otherwise
Assuming these updates are fully tested before they’re deployed, by a human, it shouldn’t be that impactful negatively that AI is being used. The problem comes when updates are moved into production without human oversight.
But it gives me the heebie jeebies, since AI is known to make and fuck shit up, and I’m stuck using MS Teams every day in my job so I see all the weird shit that vibe coding produces. I don’t relish the thought of weird, stupid shit happening to my Linux installation.
Human review of AI is sufficient in theory, but in practice it’s never as thorough as the understanding you get writing it yourself. It’s hard to avoid AI, but it is a constant invitation to laziness.
and in the process he introduced a race condition, a performance regression costing up to 9% when making reads of files around 1 MiB and dumped the responsibility of fixing his mess on co-maintainers and went on vacation.
Yeah but it sounds like three steps forward half a step back. Also, reviews/testing caught it. Sounds like the system is working. I’ve written quite a few race condition bugs in my 25 year career. That nobody caught until weeks in prod.
I understand the reluctance of AI but there’s no denying that AI in capable hands can be useful.
In capable hands. Is the real issue. Too many people believe they are capable hands.




