this post was submitted on 15 Oct 2026
32 points (70.5% liked)

TechTakes

2733 readers
141 users here now

Big brain tech dude got yet another clueless take over at HackerNews etc? Here's the place to vent. Orange site, VC foolishness, all welcome.

This is not debate club. Unless it’s amusing debate.

For actually-good tech, you want our NotAwfulTech community

founded 3 years ago
MODERATORS
 

‘The kernel project only wants serious developers. That includes having access to enough resources to function in this world’

https://www.youtube.com/watch?v=l9ARF2KcDgc&list=UU9rJrMVgcXTfa8xuMnbhAEA&index=1&pp=iAQBsAgC - video
https://pivottoai.libsyn.com/20261014-linux-kernel-goes-full-ai-slop-code-hides-chatbot-commits - podcast

time: 13 min 43 sec

all 23 comments
sorted by: hot top controversial new old
[–] self@awful.systems 30 points 1 day ago (2 children)

update: the patch set from Linus Torvalds, Boy Genius, went into review and the reviewers immediately found a race condition: https://woof.tech/@techokami/117446164348546588

wow! it's really easy to write fast kernel code when it's wrong

and now he's apparently just dumping it on someone else because he's "going on vacation", a move that post-LLM commercial developers on most teams will be extremely familiar with

[–] diz@awful.systems 6 points 6 hours ago* (last edited 5 hours ago)

By the way, his argument about "you wouldn't mention tools" is just plain wrong.

A few years back, at work, I found a security bug introduced by a commit that said something like "fix Coverity warnings". I ended up reviewing every commit that mentioned Coverity, because that legacy codebase had a lot of rather bad tricks that triggered Coverity to have a false positive.

And when a large number of false positives were getting resolved by editing code, sometimes that resulted in a false negative. E.g. Coverity complains about a memory leak, you end up with double free. Or vice versa, it complains about double free, and you end up with a leak. (The exact example was even more on the nose; Coverity complained about use-after-free, and the fix for it introduced a real use-after-free).

Bottom line is, they do not want to have those labels because that would enable someone to actually measure how good or bad LLMs are at code.

This is another thing that is extremely familiar to most commercial developers: there's an LLM-powered code review bot, but unlike any tool ever before, nobody's even trying to capture statistics whether it works or not. Why? Because whoever rolls out AI tooling isn't sure that the tooling actually works for its stated purpose, and wants to for sure get their recognition and promotion for rolling out AI tooling, without jeopardizing it with the risk of adverse KPIs.

[–] diz@awful.systems 3 points 5 hours ago* (last edited 5 hours ago)

Oh another thing, purely anekdotally, coding LLMs still suck at multithreading.

I feel that's one part where they could legitimately make actual "AI" for, basically a tool that either proves that nothing depends on exact timing, finds a counter example, or tells you it can't do either (in which case your code is probably just very bad). But big overfunded AI labs probably feel that such tooling is beneath them.

[–] supersquirrel@lemmy.ca 1 points 1 day ago

At what point does this become best considered as purposeful or accidental, targeted sabotage?