生于反抗，或是为何业余编程社区抵制 LLM 的使用

生于反抗，或是为何业余编程社区抵制 LLM 的使用
Born Against, or why hobby programming communities are against LLM usage

原始链接: https://blog.fogus.me/llm/born-against.html

小众编程爱好者社区——例如那些致力于操作系统开发、模拟器制作和代码高尔夫的群体——对使用大语言模型（LLM）的态度日益抵触。尽管这些群体常因历史上存在的“把关”行为而受诟病，但他们对人工智能的抵制源于一种根本性的哲学分歧。在这些领域中，价值并不在于最终运行的软件，而在于掌握复杂领域知识那段艰苦且漫长的过程。从业者通过多年展现出的好奇心、分享优雅的代码以及展示深刻的见解来赢得尊重。在这些爱好者眼中，大语言模型被视为一种绕过学习过程的“作弊”行为。作者认为，虽然大语言模型可以作为专家强大的助力工具，但在这些社区中，它们却取代了技艺本身。通过自动化生成代码，大语言模型剥夺了开发者原本试图获取的经验。归根结底，这些小众群体将编程的“如何”与“为何”置于产出之上，并将人工智能驱动的捷径视为偏离了他们追求的本质。

这篇 Hacker News 讨论探讨了为何许多编程爱好者社区抵触使用大语言模型（LLM）。讨论的核心在于一个根本性的分歧：爱好的价值究竟在于创造的“过程”，还是“最终结果”。传统编程的支持者认为，编程是一门工艺，其地位由技能和努力来定义。他们将大语言模型视为“兴奋剂”或“垃圾”，担心 AI 生成的代码会以低质量、衍生性的作品充斥社区，从而贬低人际交流和学习的社会价值。对于这些爱好者来说，使用大语言模型来“自动化”编程，无异于买个机器人来替自己园艺——这违背了活动的初衷。相反，一些参与者认为，大语言模型使他们能够构建原本无法负担或无法管理的应用，他们将这种工具视为一种“解决痛点”的方式，而非取代创造的乐趣。归根结底，这种摩擦源于一种担忧，即 AI 正在以自动化的噪音取代人类的联系，导致了“守门行为”——这种行为的初衷并非排外，而是为了保持爱好者社区的真实性和可控性。这场讨论凸显了人们日益强烈的愿望：将真正由人类主导的项目与 AI 辅助的自动化作品区分开来。

Born Against, or why hobby programming communities are aggressively against LLM usage

I came across a GH thread related to chess engine development that made me think of why hobby programming communities are increasingly hostile toward LLM development. While the thread doesn’t give a lot of insight into answering the question, it prompted me to think about it a bit. I’ve seen similar sentiments expressed in other niche hobby programming communities like OSDev, LangDev, TxtDev, EmuDev, RLDev, the demoscene, and code golfers. The general consensus seems to be that the knowledge that these communities work in is hard-fought and the use of LLMs is a form of missing the point entirely. In these communities (keep in mind that there is an implicit “not all…” throughout) the process of mastering a difficult field itself is the product, and something that runs is generally a nice-to-have.

Further, I’ve noticed that even in the instances where there was earnest early engagement with LLMs in some of these niche communities, the well was quickly poisoned by a combination of a lack of a deep understanding by the LLM practitioners, and a vitriolic subset of those communities that view the LLM enterprise as a form of cheating. Granted these communities have, in general, historically been characterized by feverish gatekeeping and painstakingly slow progress, so it makes sense that there might be a desire to grab some easy cachet by bursting onto the scene like the Kool-Aid man. OH YEAH…. OH NO!

In traditional niche dev circles, respect is earned slowly through years of activity in their respective fora, sharing elegant code, displays of genuine curiosity, and through sharing deep domain knowledge along the way. At the end of the day, these communities don’t care if your code works at all, but instead care that you know why and how it works. To me, an LLM functions best as a force multiplier, not a surrogate. In the hands of an expert who already understands a domain deeply, it could act like a lever. But in these niche communities, the entire exercise is in the learning. Using an LLM to generate the finished piece doesn’t make us craftsmen; it just robs us of the craft.

:F

This is the latest in my evolving thoughts on LLMs. Also see: LLMe and Mind the van Emden Gap

生于反抗，或是为何业余编程社区抵制 LLM 的使用 Born Against, or why hobby programming communities are against LLM usage

生于反抗，或是为何业余编程社区抵制 LLM 的使用
Born Against, or why hobby programming communities are against LLM usage