this post was submitted on 11 Nov 2026
183 points (98.9% liked)

Linux

15503 readers
265 users here now

A community for everything relating to the GNU/Linux operating system (except the memes!)

Also, check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] ctrlzee@lemmy.world 75 points 5 days ago (48 children)

It's an unfortunate news, burnout in open source was real even before AI. Now it has just exploded.

Reviewing code has always been a bottleneck. AI made sending a patch nearly free, but reviewing one costs the same as ever, and it lands on a few volunteers.

For code that millions run, someone has to understand every line, so the sender should do that work, not the maintainer. Otherwise you’re just moving the cost onto the people who can least afford it.

There should be a simple rule: if you can’t explain your patch line by line, don’t send it. And maintainers should feel free to reject any patch by default when the sender can’t explain it.

[–] ImgurRefugee114@reddthat.com 36 points 5 days ago (36 children)

I'm a programmer. I vibecode a bunch of prototypes and personal projects. I couldn't imagine being inconsiderate or stupid enough to submit pure hallucinated code to any project, let alone a kernel project. And to have an agent open the PR for me, with code I haven't read or don't understand? absolutely insane

[–] ctrlzee@lemmy.world 11 points 5 days ago

Same here. Vibecoding my own tools is fine, because I’m the one who pays for the bugs. A kernel patch is different: thousands of people pay for them, so understanding every line is the minimum.

Anyone who sends code to public software should follow a simple code of ethics. A low barrier to entry is great, it’s how most of us started. But the bar for responsibility should rise with how many people run your code, and right now it doesn’t.

load more comments (35 replies)
load more comments (46 replies)