写作方法2010secondactive.com
用海明威的妙招提升写作效率
Boost your productivity with Hemingway’s hack
导读
这篇文章介绍海明威的写作习惯：在写得正顺、心里还清楚下一步要写什么的时候主动停笔，让第二天有现成的起点。对写作者来说，它给出了一种对抗卡壳和空白页恐惧的具体方法，同时也提醒我们分清蓄力与拖延的边界。
可以直接用的写作要点
- 01
在写得最顺、还知道接下来要写什么时停笔，给第二天留一个明确的起点，比写到枯竭再收尾更容易续写。
- 02
场景不必一次写完，留个缺口反而方便回头把它和后续情节缝合起来。
- 03
停笔前要留下具体的下一步，否则蓄力很容易变成拖延。
- 04
这个思路可以迁移到其他创作和工作：故意留一个半成品或待解决的问题，作为下次开工的切入点。
HN 评论精选
解释了海明威技巧的机制：在场景结尾前停笔、先写后续，回来时更容易缝合，也能避开“接下来写什么”的无限选择困境。
我以前见过类似的写作建议。意思是：你可能正在写一个场景，它几乎已经写完、描述完、完成了。你在结尾前停下，转去做别的事。等你回来时，会更容易把这个场景融入故事的其他部分——甚至可能因为你已经先动手写了后面那部分，反而想清楚了这个场景之后该发生什么。这据说是为了避免陷入“那接下来该发生什么”的死循环：可选项一多，大脑就卡住了。我也觉得这属于说起来容易做起来难的那类建议，跟“低买高卖”差不多。不过我在编程时也做到过类似的效果：把写了一半的大函数搁下，去做别的功能，回来时发现可以把之前的东西拆出去复用，最后那个大函数甚至整个消失了。
BigZaphod查看英文原文
I've seen this kind of advice related to writing before. The idea is you may be working on a scene and it's almost all written/described/finished. You stop before the end and move on to something else. When you come back to the scene, you'll be able to merge it into the rest of the story more easily now - perhaps even because you've realized what needed to happen after the scene (because you moved on to start that part before you had finished the first part). This is supposed to avoid the block of wondering, "so now what needs to happen next?" where your brain starts getting stuck in a loop of endless possibility because the search space has become unbounded. I do think this is one of those "easier said than done" kind of things, similar to "buy low, sell high." However I've had days where I've done the equivalent while coding. Say, while working on an increasingly large method and then stopping because I need some additional, independent functionality. So I put the big method aside and build that functionality only to come back and notice that I can now factor out some prior stuff in this big method and call parts of the other method I was working on.. and oh if I do that again, look - more things in common! And factoring just kind of happens all before I even knew exactly what the big method originally was going to do in the first place. (In some cases, the big method just disappears entirely and there's nothing left of it.) Of course if I could make this happen all the time on demand, I'd be golden...
提醒这个技巧很容易沦为拖延的借口。
听起来很熟……这就是我拖延时干的事。
alanthonyc查看英文原文
Sounds familiar...this is what I do when I procrastinate.
警告总是停在半途、永远差一步，可能导致作品永远写不完。
不过总有风险：你可能会陷入芝诺悖论。
protothomas查看英文原文
There's always the danger, though, that you will run into Zeno's paradox.
用“留一个待解决的测试”作类比，说明如何给下一次开工留下明确、具体的起点。
这个建议也适用于软件开发。为了让自己第二天早上有焦点，故意留下一个跑不过的测试。
dws查看英文原文
This advise carries over to software development. To give yourself focus the next morning, leave yourself with a breaking test.
同类还值得读
被低估的工程技能：把文章写好
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 条写作要点编辑精选