写作与思考2021antirez.com编辑精选
编程与写作
Programming and Writing
导读
程序员兼作家 antirez 比较写代码与写文章的相通之处，评论区补充了不少来自写作教学的经验。这篇值得写作者一读，因为它把“迭代、拆解、坐下来干活”这些工程习惯翻译成了写作现场的具体做法，同时也提醒你：结构正确并不等于文章有生命。
可以直接用的写作要点
- 01
任何比邮件长的东西都要在初稿和复看之间留出间隔，隔一段时间再改，才看得见问题。
- 02
学会“杀死自己的宝贝”：分辨那些你只是因为错误理由而得意、读者并不会领情的段落，果断删掉。
- 03
越是难写的东西，初稿往往越糟，而你刚写完时恰恰最不容易察觉，所以要预设它需要大改。
- 04
把庞大难握的整体（一本书、一个应用）切成能各自解决又彼此咬合的小块：章节、场景、函数。
- 05
真正的关键是坐下来把活干完；这一条对写作者和程序员同样成立。
HN 评论精选
写作必须留出冷却期再修改，并勇于删掉自我陶醉的段落。
编程里有一个被低估、却在写作教学中被反复强调的方面：迭代。任何东西发表前都必须重读一遍；比邮件长的内容，初稿和复看之间要隔一段时间。还要学会“杀死你的宝贝”：识别那些你因错误的理由而自豪、别人并不会欣赏的东西，把它们扔进垃圾桶。越难写的东西，初稿越可能糟糕，而你写完时越不容易立刻看出来。
dkarl查看英文原文
An underappreciated aspect of programming that is taught well and consistently in the context of writing is the need for iteration. Never publish something without rereading it first. Anything longer than an email, you should have a break between writing a first draft and taking a second look at it. Murder your darlings: learn to recognize things that you're proud of for the wrong reasons, things that other people won't appreciate, and throw them in the trash. The harder something is to write, the worse your first draft is likely to be, and the less likely you are to immediately recognize it when you finish.
两者方法论相似，但创作体验与审美快感不可混为一谈。
作为程序员和想写作的人，我觉得这两件事给我的感觉完全不同。我承认它们有很多相似：都是长周期、需迭代、要注意细节、要在不同尺度上把握结构、要规划。但写散文时的手感完全不像写代码。我可以欣赏一行漂亮的代码，放一会儿再看，然后三周后开始恨它；可这跟文字在舌尖上的滋味、跟自己从脑内垃圾袋里掏出宝石让它闪光，完全不是一回事。
jonnycomputer查看英文原文
As a programmer and aspiring writer, the two activities don't really feel the same to me at all. I understand that there are many similarities. Building a piece of software and writing a novel are complex projects that span long periods of time, requires iteration, attention to detail, and cognizance of structure at varying scales, planning, etc.... But when I'm writing prose, it does not feel anything like writing code. I enjoy a beautiful line of written code, and can sit back and admire it for a while, before I get on with the business of hating it a week or three later, but it is nothing like the experience of feeling the taste of words on the tongue, of reaching into my own garbage sack of mental vomit to pull out gems to glimmer in the sun.
核心能力是把宏大难题拆成可解小块，并坚持每天到场。
两种实践有相当多共同点，包括把一个巨大而难以把握的问题（一部小说或一个应用）拆成一组更小、更易解决、又能拼成连贯整体的子问题（对象、函数、章节）。我做了多年软件开发后写第一部小说时也写过类似文章。作者说得对，关键在于出现并投入工作，这对很多人很难，但程序员已经习惯了。另外 Vikram Chandra 的《Geek Sublime》也很好地考察了写代码与写散文的联系。
diamondap查看英文原文
The two practices have quite a bit in common, including the need to break down a very large, hard-to-grasp problem (a novel or an application) into a set of smaller easier-to-solve problems (objects, functions, chapters) that fit together in a coherent whole. I wrote a similar post when, after many years of software development, I finally got around to writing my first novel. https://adiamond.me/2015/01/writing-and-programming/ The author is right in saying the key is really to show up and put in the work. That can be really hard for a lot of people, but programmers are already accustomed to it. BTW, Vikram Chandra's Geek Sublime also does a good job investigating the ties between writing code and writing prose. https://www.goodreads.com/book/show/19353724-geek-sublime Chandra goes way back, pointing out that the generative grammar we use today to describe valid programming language constructs was first created 2500 years ago in India by a guy named Panini who fully and precisely described the structure of the entire Sanskrit language. There's more on that here, if you're interested: https://medium.com/@dmitrypavluk/we-should-thank-sanskrit-for-the-21st-century-e771b6c12f14
结构正确只是及格线，作品的“魔力”来自作者独有的生命体验。
这些都成立，但这种真理漏掉了真正重要的东西。你可以写出一部功能完全正常却“死在桌上”的小说。因为好小说在形式与内容之外还有某种附加物，可以叫“魔力”，也可以说是它从一个人全部生命经验、以及他从心灵最深处解放出来的东西中汇聚而成的观察与感受的总和。科幻小说同样如此，不必显得“高雅”，但即便在相当类型化的作品里，这也是它的心脏。
scandox查看英文原文
This is all true, but it's a truth that omits the things that really matter. You can write a perfectly "functioning" novel that is dead upon the table. This is because a good novel has something beyond both its form and its content, an epi-phenomenon so to speak, which we can call "magic" or which we might say is the sum of the observations and feelings it gathers together from the total life experience of an individual and what they have managed to free from the deepest parts of their mind. This can be as true of a Science Fiction novel as of any other. It doesn't mean the work has to appear "elevated", but it is the heart of the thing even in a fairly generic work.
同类还值得读
不要想好再写，要写来思考
Don’t think to write, write to think
这篇短文主张不要把写作当成思考完成后的记录，而要把写作本身当作思考的工具：动笔的过程会逼出想不清楚的地方。
写作与思考2022 · 553 分 · 145 评4 条写作要点编辑精选写作即思考：学会自信地写作
Writing Is Thinking: Learning to Write with Confidence
这是一篇讲“写作即思考”的博客：作者认为写作不是把想好的东西誊写出来，而是借助写作本身把想法想清楚，因此写作者应当建立信心、敢于先写烂稿。
写作与思考2019 · 529 分 · 83 评4 条写作要点编辑精选如何用写作来思考
How to think in writing
这篇文章讨论的是「用写作来思考」：作者认为写作不只是把想清楚的东西表达出来，更是想清楚本身的工具——文字落在纸上，你才有机会看见自己思路里的跳跃、含混和漏洞。
写作与思考2024 · 424 分 · 120 评4 条写作要点编辑精选写作，帮你逃离默认的人生设置
Write to Escape Your Default Setting
文章的核心主张就写在标题里：写作是帮你逃离「默认设置」的手段——日常的思维和表达都有惯性默认的默认模式，而落笔能逼你跳出来，重新看清自己到底在想什么、要说什么。
写作与思考2025 · 407 分 · 93 评4 条写作要点编辑精选写作就是思考
Writing is thinking
文章以“写作即思考”为题，讨论写作不只是把已有想法记录下来，而是帮助澄清、组织和推进思考的过程。
写作与思考2025 · 330 分 · 128 评4 条写作要点编辑精选