I still think that’s not good enough, that treating them fairly is a stupid waste of time and resources and unfair to everyone else.
Just make the rule “any slop” and give the idiots a checkbox so they can ban themselves for reasons which will never be revealed to them (sloppers don’t read documents, it’ll take them a while to figure out). Also start banning people when evidence surfaces of them admitting to slopping.
I don’t like this concept that a slopper can potentially produce decent code, the data shows this simply isn’t true: sloppers produce vast amounts more and worse bugs and vulnerabilities. It’s better for the health of the project to ban it in every scenario.
How is treating one contributor fairly unfair to another contributor? If you want to add a “check this box to get your PR dumpster’d” checkbox I guess go nuts, but I’m unconvinced that’s a good long-term solution. I find it easier to ask “Do I know this contributor, or did they follow the new contributor guidelines and submit a small, single-issue PR?”, and if the answer is “no” then the PR gets ignored or, if I’m feeling gregarious and have the time, rejected with change requests. It’s a pretty easy rubric.
Humans have been perfectly capable of generating huge volumes of trash code, and code that looks good at first glance but has tricky bugs or vulnerabilities, since long before LLMs were a thing. The only real change now is the pace at which shitty code can be ripped out. IMO the solution is just: don’t accept more code than you can review and test. If that means rejecting 10x or 100x more LoC than you did five years ago, then… ok. It is more busy work, and it is annoying. But I don’t think trusting contributors to self-declare LLM use is an answer to the problem. There are better ways of rate-limiting eager beavers, regardless of what tools they use.
How is treating one contributor fairly unfair to another contributor?
Because sloppers do not actually do the work and in the vast majority of cases are not even capable of doing so. A slopper can produce 10 worthless products in the time a person can produce 1 good product.
I still think that’s not good enough, that treating them fairly is a stupid waste of time and resources and unfair to everyone else.
Just make the rule “any slop” and give the idiots a checkbox so they can ban themselves for reasons which will never be revealed to them (sloppers don’t read documents, it’ll take them a while to figure out). Also start banning people when evidence surfaces of them admitting to slopping.
I don’t like this concept that a slopper can potentially produce decent code, the data shows this simply isn’t true: sloppers produce vast amounts more and worse bugs and vulnerabilities. It’s better for the health of the project to ban it in every scenario.
How is treating one contributor fairly unfair to another contributor? If you want to add a “check this box to get your PR dumpster’d” checkbox I guess go nuts, but I’m unconvinced that’s a good long-term solution. I find it easier to ask “Do I know this contributor, or did they follow the new contributor guidelines and submit a small, single-issue PR?”, and if the answer is “no” then the PR gets ignored or, if I’m feeling gregarious and have the time, rejected with change requests. It’s a pretty easy rubric.
Humans have been perfectly capable of generating huge volumes of trash code, and code that looks good at first glance but has tricky bugs or vulnerabilities, since long before LLMs were a thing. The only real change now is the pace at which shitty code can be ripped out. IMO the solution is just: don’t accept more code than you can review and test. If that means rejecting 10x or 100x more LoC than you did five years ago, then… ok. It is more busy work, and it is annoying. But I don’t think trusting contributors to self-declare LLM use is an answer to the problem. There are better ways of rate-limiting eager beavers, regardless of what tools they use.
Because sloppers do not actually do the work and in the vast majority of cases are not even capable of doing so. A slopper can produce 10 worthless products in the time a person can produce 1 good product.