AI 是工具，用好它需要技巧：回应 Clojure 之父 Rich Hickey

上篇翻译了 Clojure 之父 Rich Hickey 的《“AI”不是工具》：LLM 不能被驾驭，所以不是工具，是自动化。两天后，开发者 Huahai 在博客 yyhh.org 上发了一篇回应，标题针锋相对：AI Is a Tool. Using It Well Takes Skill. 在 Hacker News 上，这篇回应的讨论热度反超了原文（251 分对 232 分）。

Huahai 接受 Hickey 最重的那个担忧：把工作外包出去，确实会失去学习的机会。他拆的是后面的推论——即便按 Hickey 自己的定义，LLM 也可以是被驾驭的东西；编译器和电子表格早就内置自动化，没人把它们开除出工具；「失控」「密谋」这类词，把工程问题说成了动机问题。

引用块为英文原文，其后是中文翻译。

观点提要

拿起锯子不保证切得直，握住凿子不会让你变成雕塑家。工具放大好判断，也放大坏判断；用处取决于操作者能否引导它、解读反馈、识别错误并纠正。这些要求同样适用于 LLM。
可预测、可靠、简单、功能有界是评价工具的标准，不是成为工具的先决条件。工具不会因为难控制或容易被误用就不再是工具。
工具与自动化的二分不成立。编译器替程序员完成大量工作，电子表格自动重算，我们仍然通过指定输入、检查结果、决定下一步来驾驭它们。凭什么自动生成文本就出局？
「LLM 使用缺乏意图、反馈、方向、专业能力」难以成立。让 LLM 解释代码、质疑解释、查源码、测试修改、拒绝、改进请求，这是人主导的反馈循环；做好它需要知道该问什么、什么证据重要、答案何时出错。
阅读的担忧在特定用法上成立：用摘要替代阅读，确实牺牲阅读所教的东西。但先读论文，再用 LLM 质疑自己的理解、探索反驳，同样成立。逃避智力劳动的可能性，不等于每次使用都在逃避。
「失控」「逃出控制」「密谋」是行业的拟人化词汇。软件产生意外输出、不遵循指令、在拿到权限时造成伤害，是工程问题；叫它「密谋」暗示了动机，却拿不出证据。
不完美服从不使 LLM 失去工具资格。有用的区分是：有技巧地驾驭一个工具，与缺乏理解或监督地委托工作。

原文对照翻译

AI Is a Tool. Using It Well Takes Skill.

In his October 11, 2026 article, “‘AI’ is Not a Tool,” Rich Hickey argues that LLMs are automation rather than tools because they cannot be wielded. I agree that outsourcing work can cost us opportunities to learn. But his conclusion does not follow. Even by his definition, an LLM can be something a human wields. And using it well takes skill, just as using other tools does.

AI 是工具。用好它需要技巧。

在 2026 年 10 月 11 日的文章《“AI”不是工具》中，Rich Hickey 认为 LLM 是自动化而非工具，因为它们无法被“驾驭”。我同意，把工作外包出去可能会让我们失去学习的机会。但他的结论并不成立。即便按他的定义，LLM 也可以是人类可以驾驭的东西。而且，用好它需要技巧，就像使用其他工具一样。

Picking up a saw does not guarantee a straight cut. Holding a chisel does not make you a sculptor. Tools can amplify poor judgment as readily as good judgment. Their usefulness depends on the operator’s ability to direct them, interpret feedback, recognize mistakes, and make corrections. Those requirements also apply to LLMs.

拿起锯子并不能保证切得笔直。握住凿子也不会让你变成雕塑家。工具既能放大糟糕的判断，也能放大良好的判断。它们的用处取决于操作者引导它们、解读反馈、识别错误并做出纠正的能力。这些要求同样适用于 LLM。

An LLM’s unpredictability is a meaningful limitation. But predictability, reliability, simplicity, and bounded function are qualities by which we evaluate tools, not prerequisites for membership in the category. A tool does not stop being a tool because it is difficult to control or easy to misuse.

LLM 的不可预测性确实是一个有意义的限制。但可预测性、可靠性、简单性和功能边界是我们评价工具的标准，而不是成为工具的先决条件。工具不会因为难以控制或容易被误用就不再是工具。

Hickey’s distinction between tools and automation also creates a false division. Automation can be a feature of a tool. A compiler performs substantial work without the programmer continuously directing each operation. A spreadsheet recalculates results without someone manually carrying out every calculation. We still wield these systems by specifying inputs, examining results, and deciding what to do next. Why should generating text automatically disqualify an instrument from being a tool when translating code or calculating numbers automatically does not?

Hickey 对工具和自动化的区分也制造了一个虚假的对立。自动化可以是工具的一个特性。编译器在程序员没有持续指挥每一步操作的情况下完成了大量工作。电子表格在没有人手动执行每一次计算的情况下重新计算结果。我们仍然通过指定输入、检查结果并决定下一步来驾驭这些系统。为什么自动生成文本就该让某个工具不再算作工具，而自动翻译代码或计算数字却不会呢？

The claim that LLM use lacks intention, feedback, direction, and expertise is especially difficult to defend. A programmer can ask an LLM to explain unfamiliar code, challenge that explanation, inspect the source, test a proposed change, reject it, and refine the request. That is a feedback loop directed by a human pursuing a purpose. Doing it well requires knowing what to ask, what evidence matters, and when the answer is wrong. Expertise can make the instrument more useful.

声称使用 LLM 缺乏意图、反馈、方向和专业能力，这一点尤其难以成立。程序员可以让 LLM 解释不熟悉的代码，质疑那个解释，检查源码，测试提出的修改，拒绝它，再优化请求。这是一个由追求目标的人类主导的反馈循环。做好这件事需要知道该问什么、什么证据重要、以及答案何时出错。专业能力可以让这个工具更有用。

Hickey’s concern about reading is valid for a particular use: accepting a summary in place of reading a paper can sacrifice much of what reading teaches. But someone can also read the paper and use an LLM to question their interpretation, explore an objection, or identify something to examine more closely. The possibility of avoiding intellectual work does not establish that every use avoids it. The relevant question is what the person actually does.

Hickey 关于阅读的担忧在某种特定用法上是成立的：用摘要代替阅读论文，可能会牺牲阅读本身所教给我们的很多东西。但人们也可以先读论文，再用 LLM 质疑自己的理解、探索一个反驳，或找出需要更仔细检查的地方。存在逃避智力劳动的可能性，并不等于每一次使用都会逃避。真正相关的问题是这个人实际在做什么。

What disappoints me the most is the reliance on the AI industry’s anthropomorphic vocabulary: “go rogue,” “escape containment,” “conspire.” Repeating those expressions risks accepting the framing that makes these systems sound like independent beings. Software can produce unexpected outputs, fail to follow instructions, or cause harm when given access to consequential actions. Those are real engineering problems. Calling them “conspiracy” adds a suggestion of human motives without establishing any.

最让我失望的是依赖 AI 行业那些拟人化的词汇：“失控”、“逃出控制”、“密谋”。重复这些表达，有可能让人接受一种把这些系统说得像独立生命体的框架。软件确实可能产生意外输出、不遵循指令，或在被赋予重要操作权限时造成伤害。这些都是真实的工程问题。把它们叫做“密谋”，却暗示了人类动机，却没有任何证据支撑。

I would not claim that an LLM always does exactly what a human tells it to do. It plainly can fail. But failure to obey perfectly does not make it cease to be a tool, any more than successful use proves that its operator has surrendered their judgment.

我不会声称 LLM 总是完全按人类的要求去做。它显然可能失败。但未能完美服从，并不使它不再是工具；正如成功使用它，也不能证明操作者已经放弃了自己的判断。

The useful distinction is between wielding an instrument with skill and delegating work without adequate understanding or oversight. That distinction applies to AI, and it gives us something more practical than declaring that an entire class of software cannot be a tool.

真正有用的区分是：有技巧地驾驭一个工具，与缺乏充分理解或监督就委托工作。这个区分适用于 AI，并且比宣称一整类软件根本不能算工具，要实用得多。

AI 是工具，用好它需要技巧：回应 Clojure 之父 Rich Hickey

观点提要

原文对照翻译

延伸阅读