> This makes a lot of sense to me. It relates to an idea I've seen circulating elsewhere: if a PR was mostly written by an LLM, why should a project maintainer spend time reviewing and discussing that PR as opposed to firing up their own LLM to solve the same problem? The same argument applies to open source itself. Why use someone's project when you can just have the robot write your own? It's especially true if the…
> Why use someone's project when you can just have the robot write your own? I've been thinking about this a bunch recently, and I've realized that the thing I value most in software now isn't robust tests or thorough documentation - an LLM can spit those out in a few minutes. It's usage. I want to use software which other people have used before me. I want them to have encountered the bugs and sharp edges and sanded…
The Zig project's rationale for their anti-AI contribution policy
41–50 of 496 posts
Re: The Zig project's rationale for their anti-AI contribution policy
#42It's a good rationale. But it points the finger at a real bottleneck in open source development: the burden of manually reviewing contributions. And the need to automate that with AI as well. Reviews were already becoming a problem before AI. Lots of projects have been dealing with a large influx of contributions from inexperienced developers from all over the world looking to boost their CVs by increasing their Gith…
The real bottle neck when you want to grow is connecting with the right people. An LLM is not helping with that if you want to build a community. When you use LLM to skip the need to understand a problem how are you ever going to get a reputation that I can trust?
The post is not about reputation it about seeing how people respond and work with you in a community.
EDIT: I see that you frame it as a help and a tool and sure it might work, but I feel like it is just another obstacle.
Re: The Zig project's rationale for their anti-AI contribution policy
#43Earlier quoted context omitted.
What’s the point in debating the PR quality? The policy explicitly forbids all LLM code, so that policy is of course the “real reason”.
> What’s the point in debating the PR quality? Because the pro-group are whining that the policy is preventing the merge, when in actual fact even if the policy did not exist, the PR is crap anyway.
Re: The Zig project's rationale for their anti-AI contribution policy
#44Earlier quoted context omitted.
I value software that reveals knowledge. The frontier LLMs were trained on all the code that institutions had been keeping to themselves. So they're revealing programing know-how on a scale that just wasn't possible with open source. LLMs are the ultimate Prometheus. Information is more accessible and useful now than it's ever been.
I promise you, "the code that institutions had been keeping to themselves" is not nearly as special or good as you are implying here.
Re: The Zig project's rationale for their anti-AI contribution policy
#45Earlier quoted context omitted.
A single PR for a 3000-line addition would, in all likelihood, be rejected anyway.
Doubt it: https://github.com/ziglang/zig/pull/24536
3000 line LLM commit is not that.
Re: The Zig project's rationale for their anti-AI contribution policy
#46Earlier quoted context omitted.
A single PR for a 3000-line addition would, in all likelihood, be rejected anyway.
Doubt it: https://github.com/ziglang/zig/pull/24536
Re: The Zig project's rationale for their anti-AI contribution policy
#47Re: The Zig project's rationale for their anti-AI contribution policy
#48> This makes a lot of sense to me. It relates to an idea I've seen circulating elsewhere: if a PR was mostly written by an LLM, why should a project maintainer spend time reviewing and discussing that PR as opposed to firing up their own LLM to solve the same problem? The same argument applies to open source itself. Why use someone's project when you can just have the robot write your own? It's especially true if the…
>> Whereas earlier you had to use something that was mass produced to be satisfactory for everyone As someone who recently started using OpenSCAD for a project I find this attitude quite irritating. You certainly did not "have to" use popular tools. The OpenSCAD example is particularly illuminating because it's fussy and frustrating and clearly tuned towards a few specific maintainers; there's a ton of things I'd lik…
You definitely need to have a strong sense of code design though. The AIs are not up to writing clean code at project scale on their own, yet.
Re: The Zig project's rationale for their anti-AI contribution policy
#49Earlier quoted context omitted.
Doubt it: https://github.com/ziglang/zig/pull/24536
When somebody comments PR with “Incredible work, Jacob. It is an honor to call you my colleague.” then it's safe to assume it's out of the ordinary contribution. Pretty much falling outside of the “in all likelyhood”. 3000 line LLM commit is not that.
edit Okay, I set the bar too high here with "best human developer" and vague "good AI processes". My bad. Yes, LLM is not quite there yet.
Re: The Zig project's rationale for their anti-AI contribution policy
#50Earlier quoted context omitted.
When somebody comments PR with “Incredible work, Jacob. It is an honor to call you my colleague.” then it's safe to assume it's out of the ordinary contribution. Pretty much falling outside of the “in all likelyhood”. 3000 line LLM commit is not that.
How would you differentiate a 3000 line LLM commit made by the best models and good AI processes from a 3000 line commit made by the best human developer? edit Okay, I set the bar too high here with "best human developer" and vague "good AI processes". My bad. Yes, LLM is not quite there yet.