Linux kernel memory-management code reviewer steps down due to influx of AI slop patches — volume of submissions coupled with low manpower forces the step back
Yeah, I like the idea, but those models are pretty good at parroting desirable text styles. It might become a game of whack-a-mole to identify the slop unfortunately 🫤
I think you missing the point: we don’t want slop - as in low quality code. It does not matter if it is an AI or a Human created slop.*
*: just considering the project side, not the enironmental, and ethical side.
The problem is not identifying AI slop, the problem is wasting an already limited time on a PR which seems legit until you deep dive and find that it is utterly terrible. And multiple it with a large number of PR-s because the barrier of entry to create a slop is 0.
Yeah, I like the idea, but those models are pretty good at parroting desirable text styles. It might become a game of whack-a-mole to identify the slop unfortunately 🫤
Either they get good or they don’t
If they get good, xkcd has the answer https://xkcd.com/810/
If they don’t, they keep paying for it
As always!
I think you missing the point: we don’t want slop - as in low quality code. It does not matter if it is an AI or a Human created slop.*
*: just considering the project side, not the enironmental, and ethical side.
The problem is not identifying AI slop, the problem is wasting an already limited time on a PR which seems legit until you deep dive and find that it is utterly terrible. And multiple it with a large number of PR-s because the barrier of entry to create a slop is 0.