写作方法2018amrutaranade.com编辑精选
我的写作过程
My Writing Process
导读
本文作者 Amruta Ranade 分享了自己的写作流程（研究、草稿、多轮修改等），Hacker News 的讨论则围绕“这套流程是否适用于所有写作”展开。评论者提出了更轻量的日常写作方法、写作与编程的类比，以及一个实用的写作自检框架。对写作者来说，这篇值得读，因为它既有完整的流程视角，也有“先写糙再改好”这类可以直接上手的操作建议。
可以直接用的写作要点
- 01
先写出粗糙的初稿再反复修改，比一开始就追求好句子容易得多；写作的打磨就像写代码时的重构。
- 02
动笔前先分清“内容”（要传达的事实、数据、请求）与“意图”（语气、情绪、心态），写作过程中始终想着读者。
- 03
并非每篇文字都需要研究阶段和外部评审；短小的日常写作可以直接进入草稿和修改，目标是稳定地写出“不差”的文字。
- 04
自我编辑需要知道“该看什么”，给自己建一份检查清单（信息、意图、读者、共情、结构、重写），并把它固化成流程。
HN 评论精选
不是所有写作都需要重流程；日常写作只需做到“不差”，并给出 MIIROR 自检框架。
我同意持续写出好文章很难，但我也相信持续写出“不差”的文章很容易。我们写的东西并非都长、复杂或重要到需要研究和外部评审阶段，我希望作者在草稿阶段多花些笔墨。这是我第一次听说五稿法，感觉它假定你已经知道在自己文章里该找什么问题。我正在做一个给开发者讲书面沟通技巧的通讯，核心就是引导人们注意写作时该关注什么。我把它浓缩成一个缩写（纯属好玩）：MIIROR——Message 信息：写之前想清楚要传达什么；Information 内容：事实、数据、指令、请求等；Intention 意图：语气、情绪、心态；Reader 读者：写的时候想着读你文字的人；Rapport 共情：与读者建立共鸣以提升沟通效果；Order 顺序：从概念和视觉上组织信息，让读者不迷路、不浪费时间；Rewrite 重写：写完之后再改一遍。
soneca查看英文原文
I agree that consistently good writing is hard. But I also believe that consistently not bad writing is easy. Not everything we write is long, complex or important enough to demand a research phase and external reviews. I would like the author to have spent more time in the Draft phase. It is the first time I heard about the 5-draft technique. My impression is that it kind of assumes that you know what to look for when editing your own texts. I am starting a newsletter with written communication tips for developers and my main point is to direct people to what they should be paying attention while writing. I distilled it to an acronym (just for fun): Miirror Message - before writing it, think about the message you want to communicate. Information - one part of the message is what you want to communicate - facts, data, instructions, requests, etc. Intention - another part of the message is how you want to communicate - mood, state of mind, tone, etc. Reader - while writing it, think about the person who will read your text. Rapport - one dimension of caring about the reader is about creating empathy with the reader to improve the effectiveness of the communication. Order - another dimension is about organizing your message (conceptually and visually) so your reader never feels lost or wasting time. Rewrite - after writing it, rewrite it. more detailed version: https://writingfordevelopers.substack.com/p/miirror-a-framework-for-writing
先落地粗糙初稿再打磨，写作如重构。
从很多方面看，写文章和写代码很像。两者都有很大价值先写下一个可以打磨的东西：写代码靠重构，写文章靠编辑和重写。对我来说，先写一个表述糟糕的句子再把它改好，比一开始就写出好句子容易得多，代码同理。
henrik_w查看英文原文
In a lot of ways I think writing a text is similar to writing code. In both cases, I think there is a lot of value in getting something down that can be refined. In coding, the refining is done with refactoring. In regular writing, it's editing and rewriting. I find it much easier to have a poorly formulated sentence and then editing it into shape than it is for me to write a good sentence from the start. The same applies to code for me. I have written about my process for writing blog posts here: https://henrikwarne.com/2017/11/26/6-years-of-thoughts-on-programming/
用循环阈值控制修改轮次、靠朋友反馈加速定稿的轻量流程。
过去几个月我写博客比之前多得多，最近大约每周一篇。我的流程是：1. 把要点级的想法加进待写清单；2. 决定写一篇并选主题（约 25% 来自清单）；3. 快速写出草稿；4. 检查语法、拼写和措辞；5. 如果修改超过 5 处，回到第 4 步；6. 把草稿发给朋友求反馈；7. 如果修改超过 3 处，回到第 6 步；8. 发布。整篇流程每篇文章花 1-3 小时。
Sir_Cmpwn查看英文原文
I've been blogging a lot more in the past several months than before, recently on the order of an article per week or so. My process is this: 1. Add bullet-point-length ideas to a to-write list 2. Decide to write a post and pick the subject (which comes from the to-write list maybe 25% of the time) 3. Bust out the rough draft 4. Read it for grammar/spelling/phrasing review 5. if (edits > 5) goto 4 6. Share the draft among friends for feedback 7. if (edits > 3) goto 6 8. Publish Whole process takes 1-3 hours per article.
避免居高临下地泛化他人，用第一人称经验开场更有说服力。
“是的，谁都能写，但不是每个人都能写好。”——要么她认为会写字的人没有写好的潜力（这有点自以为是），要么她本想说“但不是每个人都写得很好”（那这就是糟糕的写作）。我甚至看不出把她自己的写作经验投射到别人身上有什么意义。她完全可以不用这个别扭的开头而表达同样的意思，比如更亲切地写：“我注意到我写得不好的时候都源于流程混乱。下面这个流程帮我更稳定地写好……”
cpsempek查看英文原文
> Yes, anyone can write, but not everyone can write well. Either she thinks people who write do not have the potential to write well, or, she meant to say "...but not everyone writes well." The former is a little presumptuous, the latter is, well, poor writing. I actually do not even see the point in projecting her experiences with writing onto others. She could have gotten the same point across without the awkward introduction. It could have been framed a little more personably, e.g., "I notice that my bad writing all stems from an unstructured process. Here is the process which has helped me to write well more consistently..."
同类还值得读
被低估的工程技能：把文章写好
Undervalued Engineering Skills: Writing Well
这篇文章讨论为什么“写得好”是被低估的工程能力，以及它如何在团队协作、系统设计和职业发展中持续带来回报。
写作方法2019 · 1,109 分 · 371 评4 条写作要点编辑精选每行只写一句话：让写作和修改都更轻松的排版法
Writing one sentence per line
这是 Derek Sivers 的一篇短文，主张写作时每行只放一个句子，而不是按段落排版。
写作方法2022 · 849 分 · 297 评4 条写作要点编辑精选书面沟通是远程工作的超级能力
Written communication is remote work super power
这篇文章讨论远程工作中书面沟通的价值，评论区则补充了异步与同步沟通的适用场景，并提醒读者：备忘录、结论先行、结构化命令格式等书面沟通传统早已有之。
写作方法2020 · 831 分 · 190 评4 条写作要点编辑精选如何写出有用的文字
How to Write Usefully
保罗·格雷厄姆在这篇文章里给"有用的写作"下了一个可操作的公式：有用≈重要×新颖×正确×清楚，任一项为零，整篇文章就等于零；他还主张敢下确定判断、删掉让自己心虚的句子。
写作方法2020 · 821 分 · 285 评4 条写作要点编辑精选如何写得更清楚、想得更清楚，并学会复杂材料（PDF）
How to write more clearly, think more clearly, and learn complex material [pdf]
这份 PDF 讨论如何把文章写清楚、把思路理清楚，并用写作来学习复杂材料。
写作方法2022 · 779 分 · 153 评4 条写作要点编辑精选