写作方法2022sive.rs编辑精选
每行只写一句话：让写作和修改都更轻松的排版法
Writing one sentence per line
导读
这是 Derek Sivers 的一篇短文，主张写作时每行只放一个句子，而不是按段落排版。它值得写作者读，是因为这个排版习惯不只是视觉上的偏好：它让每一句话都成为可以单独搬动、删除、替换的单位，从而迫使你逐句检查逻辑，也让修改和协作变得更容易。
可以直接用的写作要点
- 01
把每句话单独放一行，句子的边界就变得清楚，你可以逐句检查它是否必要、是否通顺，也方便调整顺序。
- 02
一句话只承载一个意思：读者常常会跳过后面的句子，把要点拆开单独成句，能减少信息被漏掉。
- 03
修改时以句子为单位做增删替换，而不是整段重写，这样更容易看清自己到底改了什么。
- 04
写技术文档时，尽量遵循“主语—动词—补语”的顺序；一句话中出现两个动词，就考虑拆开成两句。
HN 评论精选
每行一句能让 diff 精确到句子，修改痕迹一目了然。
一个文章没提到、但对写作者特别有用的好处是版本控制的 diff：每行一句时，diff 是按句子变化的，能看出段落是怎么被重组的，比如增删或替换了哪一句，而不会显示成整段被替换。改个错别字也只涉及一行，很容易看出这次提交真正改了什么。作者有时还会把一句话拆成每行一个从句，但这属于因人而异的判断，不是硬性规则。
luhn查看英文原文
One big advantage not mentioned in the article particularly relevant to this audience: git diffs (or your VCS of choice). One sentence per line means diffs will operate per-sentence, rather than per-paragraph. This way the diff can capture the restructuring of the paragraph (adding/removing/replacing a sentence), which gives much more insight than swapping out the paragraph wholesale. It also means minor changes (e.g. typo fixes) will only add+delete a single sentence, making it much easier to identify what has actually changed from one commit to the next. I take this a step further and will often split out a single sentence into a clause per line, but this is a judgement call rather than a hard and fast rule.
每行一句对版本管理和编辑器操作都更友好。
我平时就这么做，主要因为写的东西大多放在 git 仓库里，每行一句时 diff 合理得多；而且在 vim 里，句子不跨行也更好操作。
michaelmior查看英文原文
I personally use this approach but mostly because a lot of what I write ends up in a git repository and diffs make way more sense when there is only one sentence per line. I also find things much easier to manipulate in vim when sentences don't span lines.
资深编辑的两条原则：句子按主谓补排序，内容按从大到小的语境展开。
高中时老师总说我写的东西冗长又费解。祖母让我去请教她的朋友 Sonia，她是一家知名出版社的首席审读，给包括四位诺奖得主在内的著名作家提意见。她的建议简单到只有两条：一是按“主语—动词—补语”的顺序写，如果看到两个动词，中间就该是句号；二是别把顺序搞乱，从开头写起，先找到能解释其余部分的最大语境。我并非每次都照做，但每次写技术文档时用上这套方法，效果都天差地别。
bertil查看英文原文
I remember struggling to write essays when I was in highschool. Well, I was fine, but my teachers insisted it was long-winded gibberish. Concerned, my grand’mother told me: “Ask Sonia” I knew she was her friend, and they liked to argue a lot, but I was a bit confused by the advice. It turns out, editing was Sonia’s job: she was the head reader at a very prestigious publishing house, meaning she was giving notes and feedback to very famous authors, including four Nobel Prize laureates. You kind of have to know what you are doing when you are sending a manuscript full of red in the margins and the person can respond “I’ve got a Nobel Prize and you don’t.” She definitely had the icey stare to match. Oddly, her advice was incredibly simple, and fitted in two very short pieces: * Subject, Verb, Complement –– in that order. If you see two verbs, but a period between them. * Things are confusing if you don’t put them in order: start by the beginning, find the widest piece of context that explain the rest. I don’t apply her rules every time, but for every technical document, every time I’ve tried, it’s been night and day. That typographic argument is really resonating with me.
读者会漏读段落中靠后的句子，拆成单句能提高被读到的可能。
我写邮件时必须这么做：一个段落里，第二、第三句常被大多数人直接忽略，他们还来问那些句子里已经回答过的问题，真让人抓狂，但拆成单句确实有帮助。
swamp40查看英文原文
I have to do this in my emails. Most people just ignore the second and third sentences in a paragraph. No idea why, drives me crazy - but this does help. You can tell they don't read them because they ask questions that were answered in them.
同类还值得读
被低估的工程技能：把文章写好
Undervalued Engineering Skills: Writing Well
这篇文章讨论为什么“写得好”是被低估的工程能力，以及它如何在团队协作、系统设计和职业发展中持续带来回报。
写作方法2019 · 1,109 分 · 371 评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 条写作要点编辑精选用纯文本文件写作
Write plain text files
这篇文章主张用纯文本文件写作：不依赖任何特定软件，几十年后依然能打开，还能借助 git 之类的工具记录全部修改历史。
写作方法2022 · 739 分 · 412 评4 条写作要点编辑精选