No LLM code in dependencies

No LLM code in dependencies

依赖项中不含大模型(LLM)代码

I’ve spent about 100 hours of work over the past month to make sure git-annex can build without dependencies that contain LLM generated code. At least so far. https://git-annex.branchable.com/no_llm_code/ 在过去的一个月里,我花费了大约 100 个小时的工作时间,以确保 git-annex 能够在不依赖包含大模型(LLM)生成代码的情况下进行构建。至少目前为止是这样。https://git-annex.branchable.com/no_llm_code/

Needing to review a program’s whole dependency tree on an ongoing basis is apparently what programming has come to? I’ve found some real stinkers. Large LLM generated changes being reverted in the next release without any explanation. An incoherent 1489 line commit message with 10,000 lines of changes to a 26,000 LOC code base. A LLM prompt to copy code from another project that seems to have only avoided being copyright infringement due to luck. 难道编程现在已经沦落到需要持续审查程序整个依赖树的地步了吗?我发现了一些非常糟糕的情况:大模型生成的代码在下个版本中被毫无解释地回滚;在一个 26,000 行代码库中,出现了包含 10,000 行变更、且提交信息长达 1489 行却逻辑混乱的提交;还有通过大模型提示词从其他项目复制粘贴代码,仅仅因为运气好才勉强避开了版权侵权。

I now have additional information about the quality of dependencies which will surely influence future decisions. As far as I can see, that’s the only positive benefit of this work. 我现在掌握了更多关于依赖项质量的信息,这无疑会影响我未来的决策。据我所见,这是这项工作唯一积极的收获。

I realize that I am probably trying to hold back the tide at this point. That appears to be why Software Freedom Conservancy punted, and I doubt that the FSF will do any better. As these dominos fall, I am reconsidering my participation in these communities. But I continue my work and support my users. 我意识到,在这一点上我可能是在试图阻挡潮流。这似乎就是软件自由保护组织(Software Freedom Conservancy)选择放弃的原因,我也怀疑自由软件基金会(FSF)能做得更好。随着这些多米诺骨牌倒下,我正在重新考虑我是否还要继续参与这些社区。但我会继续我的工作,并支持我的用户。

It may seem easy to prompt a LLM with “Add fourmolu config and restyled neat format a module” and commit the result and call yourself a 10xer. But please consider the broader impact of your actions. (In the above case, that project lost my further collaboration on it.) 给大模型发送指令“添加 fourmolu 配置并以整洁格式重构模块”,然后提交结果并自诩为“十倍速程序员”,这看起来似乎很容易。但请考虑一下你行为的更广泛影响。(在上述案例中,该项目失去了我后续的协作。)