写作即思考 · Writing Is Thinking

写作不是把想好的东西誊写下来,而是想清楚的过程本身

最深的误解是把写作当成"思考的输出"——以为脑子里先有完整想法,写只是抄录。真相相反:在写下来之前,你以为自己懂了,那只是"理解的错觉"——感觉清晰,一落笔就发现处处是窟窿。写作能戳破这层错觉,因为它强制串行化:思维在脑中是并行、联想、网状的,而句子是一条线。把网压成线,你必须回答脑子能糊弄过去的问题——谁先谁后?什么导致什么?这一步在哪断了?

非平凡点:① 纸面是一块不会衰减的外置工作记忆。人脑只能同时握住三四个组块,复杂论证必然溢出;写下来把中间结果外置,你便能驾驭远超脑容量的复杂度。② 写作是思维的编译器——直觉里语焉不详处,写成句子就编译不过,逼你当场补上缺失的定义。③ 与佛学观照同构:内观(vipassana)让自动升起的念头变得"可被观察";写作让模糊的念头落到纸上、成为可审视的对象,在你和你的想法之间撑开一道缝。④ 对照分布式系统:纯在脑中想是"最终一致、且无日志"的状态,自己都无法重放;写下来则是一条append-only 日志,可回看、可审计、可定位哪一步出错。

实践:为了发现而写,不是为了记录而写。初稿就是"在纸上思考",它本该难看——把"生成"和"修改"分成两趟,别让内心编辑在你还没想清时就掐死你的探索。

脑中:并行联想网 串行化 纸面:一条线 断裂 = 你没想清的地方
把网状思维压成线性句子,断点暴露出你以为懂、其实没懂之处
经典例子

物理学家费曼晚年,一位历史学家看着他满桌的草稿,说这是他思考过程的"记录"。费曼当场纠正:这不是记录——纸上发生的就是思考本身,我是真的在纸上做出来的那些工作。这句话点破了写作的本质:方程和涂改不是事后留痕,而是认知发生的现场。同理,"如果你不能把它写清楚,说明你还没真懂"——讲不清往往不是表达问题,是理解还没成形。

场景 · BigCat

① 工程:动手写 AI agent 系统前先写设计文档——文档不是给"已完成的设计"留档,而是设计在被写出来时才暴露出它是坏的:当你被迫把多个 agent 的调用时序逐步写成句子,那个在脑中一直被跳过的竞态条件才终于现形。② 育儿:给学龄孩子讲清一个概念前,先逼自己用三句话写下来——你会精确地发现自己理解里最虚的那块,往往正是孩子会卡住的那块。写不出,等于还没真懂。


Writing Is Thinking — writing isn't transcribing finished thoughts; it's the process that makes fuzzy thought precise. Before you write, you feel you understand — that's the illusion of explanatory depth. Writing breaks it by forcing serialization: thought is a parallel associative graph, prose is a single line, and flattening the graph forces you to answer what your intuition glossed over — what comes first, what causes what, where the chain breaks. The page is an external working memory that doesn't decay (your head holds only ~4 chunks), a compiler that won't pass vague sentences, and an append-only log you can replay. Practice: write to discover, not to record — let the first draft be ugly, and split "generate" from "edit."

中文提示词
这是我对 [主题/决策] 的初步想法(粗糙、未整理):[贴上你的草稿/要点]。 请把它当成"我在纸上思考",帮我用写作戳破理解的错觉: ① 指出 2-3 处我以为讲清了、其实有逻辑断裂或缺定义的地方; ② 对每一处,提出一个我必须回答才能想清楚的尖锐问题; ③ 不要替我润色成漂亮成稿,目标是让我看见自己还没想透的地方。
English Prompt
Here are my rough, unsorted thoughts on [topic/decision]: [paste your draft/notes]. Treat this as me "thinking on paper" and use writing to break my illusion of understanding: 1. Point out 2–3 places I think I explained but where the logic actually breaks or a term is undefined. 2. For each, pose one sharp question I must answer before I can think it through. 3. Don't polish it into clean prose — the goal is to expose what I haven't actually figured out.

一次只说一件事 · One Idea at a Time

每个句子承载一个想法,每个段落证明一个论点——读者的工作记忆是瓶颈

核心约束不在写者,而在读者:人的工作记忆一次只能握住三四个组块。一个句子塞进三个想法,读者就得同时解析、暂存、关联三件事——超载,于是回读。回读一次,阅读的"吞吐量"就崩了。所以"一次只说一件事"不是修辞品味,是尊重读者认知带宽的物理纪律

非平凡点:① 复杂度守恒。你写时没替读者理顺的那团纠缠不会消失——它被原样转嫁给每一个读者,再乘以人数。写者多花十分钟拆清楚,等于替一千个读者各省下解码的力气。这正是工程师熟悉的取舍:在写入时压缩,还是把解压成本推给每一次读取。② 想法的边界就是修改的单元——一个句子怎么拆都别扭,往往说明底层那个念头本身还缠绕着(接 Card 1:浑浊的句子是浑浊思维的影子)。③ 与单线程事件循环同构:高吞吐来自把任务切小、快速流过,而非一个巨型阻塞调用——一句一事,就是给读者的大脑喂小任务。④ 句内也有顺序契约:每句以"旧信息"开头(给读者一个锚),以"新信息"结尾,让新知识挂靠在刚立住的旧知识上,链条才不断。

实践:一句话 = 一个主语做一件事。当你写出"……而且……其中……因为……"层层套叠时,停下,拆开。检验法:读者能不能用一个短句复述这句话的要点?不能,就还没拆够。

经典例子

科学论文摘要是这条纪律的极致训练场:在严格字数内,每一句只推进一步——背景一句、缺口一句、方法一句、结果一句、意义一句。读者(审稿人)能在三十秒内重建整篇逻辑,靠的不是句子华丽,而是每句只搬一块砖、且每块砖都压在上一块上。删掉任何一句,链条就缺一环——这是"一句一事 + 旧信息开头"两条规则叠加的效果。

场景 · BigCat

① 工程:技术评审里,一个逻辑改动一个 commit、一句话一个论断。一个改了三件事的 200 行 commit,正是散文里那种塞了三个想法的长句——评审者被迫并行解析,看不动。把它拆成三个小 commit,等于把长句拆成短句。② 育儿:给学龄孩子下指令,"先收玩具,然后洗手,再来吃饭"一次说完,孩子的工作记忆装不下三步,多半只执行最后一步。一次一件,做完再说下一件——和写作完全同理。你不替读者/听者切小,认知超载就由他们买单。


One Idea at a Time — one idea per sentence, one point per paragraph. The bottleneck isn't the writer but the reader's working memory (~4 chunks). A sentence packing three ideas forces the reader to parse, buffer, and relate them at once → overload → reread, and throughput collapses. Key idea: complexity is conserved — tangles you don't resolve as writer are dumped on every reader, multiplied by readership (compress at write-time, or pay decompression cost on every read). The idea boundary is the unit of revision: a sentence that resists splitting often signals a still-tangled thought. Follow the given-new contract — start each sentence with old information (an anchor), end with the new. Test: can the reader restate the sentence in one short clause?

中文提示词
这是我写的一段文字:[贴上段落]。 请按"一次只说一件事"帮我做认知带宽审计: ① 找出装了 2 个以上想法、会让读者回读的句子,逐句标出来; ② 把每个这样的句子拆成若干"一句一事"的短句,并尽量让每句以旧信息开头、新信息结尾; ③ 指出这一段到底想证明哪一个论点——如果它其实在证两件事,建议怎么拆成两段。
English Prompt
Here is a passage I wrote: [paste paragraph]. Audit it for reader cognitive bandwidth, using "one idea at a time": 1. Flag every sentence carrying 2+ ideas that would force a reread. 2. Split each into "one idea per sentence" clauses, and where possible start each with old info and end with new. 3. Name the single point this paragraph is meant to prove — if it's actually proving two, suggest how to split it into two paragraphs.

主动语态 · Active Voice

"谁,做了,什么"——主动语态强迫你指名道姓,被动语态最擅长藏人

主动语态的结构是"施事 → 动作 → 受事",正好对齐现实的因果结构,也对齐大脑天生用"谁干了什么"来建模事件的方式。被动语态把施事者藏起来——"出现了一些失误"——句子语法完整,但那个该负责的"谁"凭空消失了。被动有时正是为了藏人,而这恰恰是它最值得警惕的信号。

非平凡点:① 语态不只是风格,是一种本体论选择:主动语态强迫你把"谁"和"什么"都填满,隐藏的假设与缺失的责任主体便被逼现形。② 工程文档里被动语态是 bug 的藏身处——"数据会被处理"隐去了:哪个服务、什么时候、给了什么保证?被动语态 = 因果图上一条悬空的边,主动则逼你把它接到一个具体节点上。③ 主动通常更短更快读:被动要多出"被/由……所"这类支架,每句都让读者多解一层。④ 但要分寸:当受事才是话题、或施事者未知/无关时,被动是对的——"样本被加热到 80°C",关注点本就在样本而非谁动的手。规则是"默认主动,刻意被动",不是"消灭被动"。

实践:扫一遍草稿里所有"被 / 由 / 得到了……",每一处问一句:这个动作的施事者是谁?我是有意藏他,还是只是偷懒? 没有理由藏,就改成主动,把"谁"请回句子里。

经典例子

"Mistakes were made(出现了一些失误)"是英语世界政治辞令的标本——承认了有错,却让犯错的人神秘缺席。乔治·奥威尔在《政治与英语》中早已点破:含混的被动语态加上抽象名词,是政治语言用来掩盖责任、麻痹判断的标准工具。语态在这里不是文采问题,是诚实问题——主动语态会逼出那个被刻意省略的主语。

场景 · BigCat

① 工程:故障复盘里,"数据库被打挂了"和"重试逻辑反复猛击数据库导致它过载"是两份不同的文档——前者没有可修的对象,后者直接指向施事者、也就指向了修复点。被动语态的复盘读起来像没人有错,于是也没人会改。② 育儿:示范诚实的能动性。"花瓶碎了"把孩子(和你自己)的手从句子里抹掉了;如实说出"谁、做了、什么",才是在教责任。主动语态是写作层面的"风险共担"——把名字留在句子里。


Active Voice — active voice is "actor → action → object," matching the causal structure of reality and how the mind models events. Passive voice hides the agent ("mistakes were made") — which is exactly why it's a tell. Voice is not just style but an ontological choice: active forces you to name who does what, surfacing hidden assumptions and missing actors. In a design doc, passive is where bugs hide — "the data is processed" omits which service, when, with what guarantee (a dangling edge in the causality graph). Active is usually shorter and faster to parse. But nuance: passive is right when the object is the topic or the actor is unknown/irrelevant ("the sample was heated to 80°C"). The rule is "default active, deliberate passive," not "ban passive."

中文提示词
这是我写的文字(如设计文档/复盘/通知):[贴上文字]。 请帮我做"语态与责任"审计: ① 找出所有被动句,逐句标出被隐去的施事者是谁; ② 对每一处判断:藏掉这个"谁"是有意的(受事才是话题)还是偷懒?偷懒的改成主动; ③ 特别标出那些"让没人需要负责"的句子——把它们改写成指名道姓、能指向修复点的主动句。
English Prompt
Here is something I wrote (e.g., a design doc / postmortem / announcement): [paste text]. Run a "voice and accountability" audit: 1. Find every passive sentence and name the agent it hides. 2. For each, judge whether hiding the actor is deliberate (the object is genuinely the topic) or just lazy — rewrite the lazy ones as active. 3. Flag sentences that make "no one responsible," and rewrite them as active sentences that name the actor and point to a fixable target.

删除胜增补 · Subtraction Beats Addition

"删去多余的字"——好文章主要靠减出来,而不是加出来

人改进任何东西的默认本能是"加":加一段解释、加一个限定、加一句过渡。研究反复显示,面对一个待改进的对象,人压倒性地选择增补、几乎想不到删减。但写作恰恰主要靠变好。每一个字都在花读者的注意力预算,一个不挣钱的字,就是对每一位读者征收的净税。

非平凡点:① 减比加难,有两个原因。其一,减是隐形劳动——加东西有新成果可展示,删东西看不出你干了活。其二,损失厌恶——你在杀自己亲手生出来的字("kill your darlings",忍痛删掉最得意的句子)。② 最深的删除不是删字,是删想法:最勇敢的一刀往往砍掉你最自豪、却不服务读者主线的那一整段。判准永远是读者的路径,不是你的不舍。③ 减法会复利:删掉最弱一环,既抬高平均水准,又移除一个失效点——这正是否定之道(via negativa)、YAGNI、奥卡姆剃刀共享的逻辑:通过移除而变强,比添加更稳。④ AI 时代这条模型权重在上升:生成已廉价到无限,稀缺的能力从"写得出"转向"敢删、会删"——把模型吐出的洋洋洒洒砍到只剩骨头。

实践:先写长,再砍掉三成。 逐句问一句:删掉它,读者会失去任何他真正需要的东西吗?不会——删。把"删除"单独安排成一趟,戴着"减法的眼睛"去读自己的稿子。

经典例子

写作圣经《风格的要素》把整本书压成一条铁律:"删去多余的字"(Omit needless words)——有力的文字是精炼的,一个句子不该有多余的字,正如一幅画不该有多余的线条。还有那句广为流传的话:"这封信写长了,因为我没时间把它写短"——写短比写长更费功夫,因为短意味着你已经替读者把删减的苦活全干完了。删,从来不是偷懒,而是更高阶的劳动。

场景 · BigCat

① 工程:最好的 PR 常常是净删行的——删掉一个功能、一个配置项,等于一次性移除它带来的维护成本和整片 bug 暴露面。"今天我让代码库变短了"往往比"我加了个功能"更有价值。② AI 工作流:你让模型起草,真正决定质量的是你之后那把删减的刀——把三页删到半页,留下的密度才是你的判断力。③ 沟通:少说,未说的部分自带分量。对文字、对代码、对话语,减法都是被严重低估的那半门技艺。


Subtraction Beats Addition — our default instinct when improving anything is to add; research shows people overwhelmingly add rather than subtract. Yet writing improves mostly by cutting. Every word spends the reader's attention budget, so a word that doesn't earn its place is a net tax on every reader ("omit needless words"). Subtraction is harder for two reasons: it's invisible labor (nothing new to show), and it's loss-averse (you're killing words you birthed — "kill your darlings"). The deepest cut isn't words but ideas: deleting the paragraph you're proudest of because it doesn't serve the reader's path. Subtraction compounds — removing the weakest link both raises the average and removes a failure mode, the shared logic of via negativa, YAGNI, and Occam. In the AI era, when generation is free, the scarce skill shifts from producing to cutting. Practice: write long, cut 30%, edit in a dedicated deletion pass.

中文提示词
这是我写的文字:[贴上文字]。请戴上"减法的眼睛"帮我删,目标是砍掉约 30% 而不损失任何读者真正需要的信息: ① 逐句标出可删的冗词、套话、空过渡,给出删后版本; ② 找出 1-2 处"我可能最得意、但其实不服务主线"的句子或段落,建议忍痛删掉,并说明删了为何更强; ③ 给出精简后的全文,并告诉我字数减少了多少。
English Prompt
Here is something I wrote: [paste text]. Put on a "deletion mindset" and cut it by ~30% without losing anything the reader genuinely needs: 1. Mark deletable filler, clichés, and empty transitions sentence by sentence, and show the trimmed version. 2. Identify 1–2 passages I'm probably proudest of that don't serve the main line — recommend cutting them and explain why the piece is stronger without them. 3. Return the tightened full text and tell me how many words it dropped.