Earlier quoted context omitted.
I really hope that you have gone over what the LLM decides to do. Time and time again I've had a project (such as a DSL to SQL compiler, automatic Rust codegen, CSS development) stall because the LLM took a short sighted decision. I later found better solutions by querying Reddit and upon consulting the LLM, it basically said "oh shit I'm sorry"
We have all had that experience, that's just the way this new world is. It's honestly pretty arrogant to tell a senior engineer that you "really hope" they've gone over some code. AI generated or otherwise.
The Zig project's rationale for their anti-AI contribution policy
471–480 of 496 posts
Re: The Zig project's rationale for their anti-AI contribution policy
#472Earlier quoted context omitted.
"They may speed up the good programmers a little, but those people were able to program anyway without LLMs." I don't think this is realistic. I'm a good programmer, and it speeds up my work a lot , from "make sense of this 10 repo project I haven't worked on recently" to "for this next step I need a vpn multiplexer written in a language I don't use" to, yeah, "this 10k line patch lets me see parts of design space we…
It's great when I know how the code should look. Sometimes I just can't bring myself to write yet another http handler.
Re: The Zig project's rationale for their anti-AI contribution policy
#473Founders go 1000x your own projects and leave real programmers alone.
Re: The Zig project's rationale for their anti-AI contribution policy
#474Earlier quoted context omitted.
but that doesn't have anything to do with LLMs. if someone made the same gigantic mess of a PR without LLMs, it would still be rejected, because it is a gigantic mess of a PR. the low effort part is the problem. what if i made a great, focused, readable PR but had claude write it out? what if i carefully checked and deliberated each line, just as if i had written it myself? granted, in the real world, 99.9% of slop P…
Well previously lazy contributors simply would never have made a PR because it was too much work. Now they can have an LLM make a PR with virtually no effort at all. It’s obviously an imperfect rule, and maybe it’ll change over time. But I am just saying that I understand why open source maintainers are doing this. There is just no possibility for them to review all the low effort AI slop being thrown their way. Yes,…
Re: The Zig project's rationale for their anti-AI contribution policy
#475Earlier quoted context omitted.
People forget that LLM code cannot be covered by copyright. So LLM code cannot be placed under an open source license
This is overstated. Not all LLM code is produced the same way. Code produced through substantial human creative input still falls under copyright, at least the way things are now. Besides, nothing legally prevents placing code under a license. Enforceability is the question, not permission. It's a bit like saying speed limits don't apply on private property, therefore you can't have any traffic rules on your private…
That’s not how copyright works. If you don’t own the code, you can’t release it under a license. The question of how much human editing is needed to establish copyright is a huge question right now.
Re: The Zig project's rationale for their anti-AI contribution policy
#476Earlier quoted context omitted.
We have all had that experience, that's just the way this new world is. It's honestly pretty arrogant to tell a senior engineer that you "really hope" they've gone over some code. AI generated or otherwise.
Sorry. I forgot to add to add the respect form I really hope usted checked your code At this point I'm pretty sure I did the homework for people in college who are now senior engineers
This is commonplace. So commonplace that most have worked “checking the LLM” into their workflow so deeply that essentially all that’s done is prompt followed by a mini code review.
To suggest a senior engineer blindly accepts modifications without code review kinda hints at you not using LLMs to realize how quickly it will make a mess of things if you don’t hold it’s hand.
Re: The Zig project's rationale for their anti-AI contribution policy
#477Earlier quoted context omitted.
This is funny because I was in the same situation, and actually used Claude to make a custom CAD program inspired by OpenSCAD :) https://fncad.github.io 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.
This is a good example of what I mean! fnCAD appears to be a significantly buggier and highly incomplete version of OpenSCAD, where AI essentially grabbed the low-hanging fruit - albeit an impressively large amount of fruit - and left you with the hard parts. I fail to see how this solved any problems. Maybe it was an experiment, which is fine. But it's not even close to a viable CAD product, even by OpenSCAD's scruf…
I mean, to be fair, a one-user project is not ever going to be as bugfree as a tens-of-thousands-of-users project. That's just inherent and not an AI issue. If you judge AI projects by that standard, they'll always come up short. It's a sampling issue. An AI project that's gotten to a level where it competes with a traditional project will always be buggier and less feature complete and polished, because AIs speed up development. It will simply have seen far less, well, polish to get there.
Re: The Zig project's rationale for their anti-AI contribution policy
#478Earlier quoted context omitted.
> There may be very simple codebases where an LLM can actually give you "thorough documentation" or "robust tests", but those are rare. Its not rare. I've built 2 dozen line-of-business apps in it last handful of years that were glorified CRUD apps. Every environment I've been in has had a mix of the 2. And even then, that's at odds with your absolute above. On top of being in a field that changes daily.
You are interpreting a general statement as a categorical one. I wasn't really going for an exact, formal statement, but I can give you a formal interpretation of what I said above, if you want to be pedantic. In general, you can't expect an LLM to produce thorough documentation or robust tests for nontrivial software, because the use of those software (i.e. how their interfaces are expected to behave) contains assum…
That is in fact what I did and if you meant otherwise, then yes I agree that currently there are plenty of cases in which those tools fall short and will never replace a human.
Re: The Zig project's rationale for their anti-AI contribution policy
#479Earlier quoted context omitted.
I agree, but the problem comes back to how to evaluate quality at scale. That is very hard. It’s easier to just say no AI because that at least turns off the fire hose.
It sounds like they are even rejecting submissions where they even get a whiff of ai being "consulted" though. That's not quite the same as turning off the firehose.
The discourse around AI in the arts, and other creative and craft fields, is utterly identical to the discourse around photography when it came out to the point that you could search and replace terms and have the same dialogue.
Re: The Zig project's rationale for their anti-AI contribution policy
#480Earlier quoted context omitted.
yep. as an expert programmer there are things i did not have access to. for example, i have an embedded-lite hardware project that required a one line patch to a linux kernel Module. i know what a kernel module is and im reasonably certain that the patch is safe, but there is no way in hell i would have found that solution (i would have given up). in a world without llms, the project would have died.
I really hope that you have gone over what the LLM decides to do. Time and time again I've had a project (such as a DSL to SQL compiler, automatic Rust codegen, CSS development) stall because the LLM took a short sighted decision. I later found better solutions by querying Reddit and upon consulting the LLM, it basically said "oh shit I'm sorry"
we have 2 very high value DAU, one of whom is me, and probably will max out at 1000 in our wildest dreams.
long term, our biggest concern is a security regression that lets outsiders see our internal information