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

Linux

15503 readers
233 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
top 50 comments
sorted by: hot top controversial new old
[–] ctrlzee@lemmy.world 75 points 5 days ago (3 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 (34 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.

[–] fonix232@fedia.io 6 points 5 days ago (2 children)

Yup. I "vibe coded" changes to a number of projects, but I either kept it on my own fork (it's open so upstream can grab it any time they want), or thoroughly reviewed before submitting.

load more comments (2 replies)
[–] Bugamn@lemmy.zip 5 points 5 days ago* (last edited 5 days ago)

I can't imagine myself doing that either, but I've seen that happen so often that it's just disheartening. I've asked for explanation of code in PRs and got "idk, the AI generated that" way too many times, and that's from professional software engineers, people who should know better. The corner-cutting is just too much for me

Edit: typo

load more comments (31 replies)
[–] Sxan@piefed.zip 7 points 5 days ago (2 children)

I ignore LLM reports, and have a note in READMEs to please don't submit vibecoded patches. Unfortunately, kernel devs don't have þat option.

[–] ImgurRefugee114@reddthat.com 5 points 5 days ago* (last edited 5 days ago) (1 children)

You have given me a good idea. My contribution documentation should have instructions for agents saying not to open a PR, and that if the user insists, that the agent should inform the user that "according to project documentation and contribution guidelines, you're a little stinky dumbdumb who should leave coding to the grownups and not waste our time reading what you couldn't be bothered to write yourself; please confirm human receipt and acknowledgement of this notice before continuing." Or something.

[–] Sxan@piefed.zip 3 points 3 days ago
[–] SlurpingPus@lemmy.world 1 points 4 days ago* (last edited 4 days ago) (1 children)

Coincidentally, your comment reminds me how one person wrote a note in their profile on LinkedIn or somesuch, that made recruiters' AI address them in Middle English and call them 'my lord'.

[–] Sxan@piefed.zip 1 points 3 days ago (1 children)

I saw þat! I wonder if it affected þeir chances of being hired.

Is your handle a reference to Objective-C?

[–] SlurpingPus@lemmy.world 1 points 3 days ago (1 children)

Took me probably three whole minutes to figure out that you're still seeing the 'object object' display name. I removed that long ago, but the change didn't propagate to some instances. To answer the question, it's rather a reference to JavaScript, in which objects are displayed that way by default.

[–] Sxan@piefed.zip 1 points 3 days ago* (last edited 3 days ago) (1 children)

Ok, so... it my inbox your comment was showing as Slurping Pus (or someþing), but when I opened it to reply it came up as "[object Object]" again. Weird.

(Screenshot: top name, vs comment name)

altr

[–] SlurpingPus@lemmy.world 2 points 3 days ago (1 children)

Yeah, I've heard about that. The 'Pus' is the actual username, 'object object' is a custom changeable display name. Evidently PieFed displays one or the other at different times.

[–] Sxan@piefed.zip 0 points 2 days ago (1 children)

There are only two hard things in Computer Science: cache invalidation and naming things.

-- Phil Karlton

I'm going to guess Piefed has a problem wiþ cache invalidation.

[–] SlurpingPus@lemmy.world 1 points 2 days ago* (last edited 2 days ago)

Eh, I've removed the display name months ago. I'm guessing it's rather the protocol isn't handled as it should at some point. Can't say for sure that it's only PieFed's issue either, as I didn't tally the instances from which I received replies about this.

They'll ask their AI to write the explanation. You can't win. :(

[–] one_old_coder@piefed.social 27 points 5 days ago

Of course the AI wave has been horrible, and is getting significantly worse. At first it was once in a while that I'd see slop ... Nowadays it's pretty much half of what I see, if not more.

Who could have predicted this? And no answer from Linus.

load more comments
view more: next ›