写作方法2018gwern.net编辑精选
什么是晨间写作效应？
What Is The Morning Writing Effect?
导读
这篇 Gwern 文章讨论“晨间写作效应”：为什么许多写作者在早晨状态更好，以及睡眠、作息类型和任务性质如何影响写作。对写作者来说，值得读的是它把写作时间安排当作可实验的习惯问题，而非单纯意志力。
可以直接用的写作要点
- 01
把需要情绪投入和深度构思的写作放在一天中精神最清醒、干扰最少的时段，别拖到精疲力竭再写。
- 02
写作比编程更像开放性问题：没有清晰路线图，也难判断何时完成，因此要用固定时段和外部截稿来降低不确定性。
- 03
不要迷信“晨型人/夜型人”标签；多数人处于中间，可通过一段适应期训练出适合自己的写作节奏。
- 04
利用睡眠和闲暇后的孵化效应：睡前留下问题，早晨或散步、远足后先记录冒出的想法。
HN 评论精选
写作比编程更耗情绪，且作息类型可以通过训练调整。
个人体会：我白天会经历很多“自我损耗”，有孩子后更明显，晚上根本写不动，脑子太累。同时写代码和写作的人会发现，写作在情绪上消耗大得多：编程是解决问题，通常有清晰路径，也知道何时算解决；写作模糊、不成形，几乎没有路线图，也永远不知道何时算“写完”。另外，晨型人/夜型人的刻板印象被夸大了。大学时我是彻底夜猫子，晚上10点到凌晨2点效率最高；进入职场后被迫变成晨型人，痛苦过渡后反而喜欢早晨，6点到10点状态最好。18年后我仍是“晨型人”，但偶尔熬夜时“夜猫子”倾向很快短暂回归。不过我需要8—9小时睡眠，不可能同时做两者。研究似乎表明大多数人介于两者之间，对这些人来说，可以把自己训练成想要的类型。
weehobbes查看英文原文
Few thoughts: For me personally, I experience a lot of ego depletion during the day. But having kids tends to do that. There's no way I can write at the end of the day, I'm just way to mentally tired. Also as someone who both codes and writes, writing is far more emotionally taxing. Coding is problem solving - there is usually a clear path to follow and I generally know when I've solved a problem. Writing for me is unclear and amorphous. There is almost never a road map, and I never really know when I've "finished." Finally, I think that lark/owl stereotypes are overblown. Up through college, I was absolutely an owl and did my best work from 10pm to 2am. Once I entered the workforce, I was forced into becoming a lark and after a painful transition, loved mornings and did my best work from 6am to 10am. 18 years later, I'm still a "lark" but from time to time, I have to pull late nights and my "owl" tendencies come back quite easily for short periods of time. But I need 8-9 hours of sleep... I can't do both lark and owl at the same time. I think studies show that the vast majority of people are in the middle - neither larks nor owls, and for those people, I believe you can train yourself to be whichever one you want.
夜间写作适合情绪和经验驱动的内容，晨间习惯适合长期理性的项目。
这本质上是个经验之谈：卡夫卡、乔伊斯、聂鲁达、艾略特等都在夜里写作。我的工作假设是“浪漫主义/情感主义 vs 抽象理性主义”：如果你写的东西受益于即时经验和情感输入（比如卡夫卡在保险公司工作一天后写噩梦般的官僚制度），那最好在夜里写，等白天的事发生、头脑已运转12小时以上再动笔。反过来，如果你在做庞大宽泛、需要长期持续努力和清醒头脑的项目，早晨的固定习惯更有利于一步步推进。
keiferski查看英文原文
It’s fundamentally an anecdotal thing: Kafka, Joyce, Neruda, Eliot, etc. all wrote at night. My working theory is something like “romanticism/emotionalism vs. abstract rationalism”; if you’re writing something that benefits from immediate experience and emotional input (e.g. Kafka writing about nightmarish bureaucracy after working all day in an insurance firm) then it is better to write at night, after the events of the day have happened and your mind has been operating for 12+ hours. Alternatively, if you’re working on a large, broad project that requires long-term, sustained effort and a clear mind, a morning habitual routine is better for making step-by-step progress.
睡眠和闲暇后的孵化效应能带来好点子，晨间或休息后适合写作。
我写得很多：过去35年平均每一年半写一本书。下面这点可能是关键：“也许睡眠本身才是关键：除了重置状态，睡眠还负责记忆形成，并似乎参与无意识的创造过程。”我发现早晨是写作、设计或写软件的最佳时段，好点子常常早晨就摆在那里。不过，如果我下午去休闲（比如远足一下午），晚饭后也常得到同样效果。
mark_l_watson查看英文原文
I write a lot: probably average writing 1 book every 1 1/2 year over the last 35 years. This may be key: “Yet another version might be that sleep itself is the key: sleep, aside from any resetting, is also responsible for memory formation and appears involved in unconscious processes of creativity.‘ I find the morning is my best work time for either writing or designing and writing software. It seems that often good ideas are just there for the taking in the morning. That said, I often get the same effect after dinner if I have taken the afternoon off for leisure (e.g., hiking all afternoon).
写散文偏早晨、编程偏夜晚，可能因为编程更怕被打断。
我最初的问题是：写散文和写代码有何不同？文章提到了：“尽管表面相似（都主要是处理文本），软件开发与写作的时间节律却截然不同。回想起来，我不记得有‘清晨编程’潮流；程序员以晚到和深夜编程闻名，尤其在大学，可能通宵。有趣的是，写作与编程的刻板印象和 RescueTime 数据完全吻合。”我很想进一步弄清两种活动为何在时间表上相反。就我而言，写散文（主要是文档、博客文章和产品计划）喜欢早起在早晨做；编程则更喜欢夜里。我的直觉是：夜里打断更少，而编程时打断更烦人。还有谁也既写作又编程：两者会用同一时间表吗？
sqs查看英文原文
My first question was about how writing prose differs from writing code. The post covers this: > despite being apparently similar activities (both mostly involve slinging text), the temporal timing of software development & writing are strikingly different. Thinking back, I don’t recall early-morning programming being a trend among programmers (programmers are infamous for preferring to come in late and late-night programming sessions which may wrap around the clock, especially in college). It’s fascinating that the stereotypes about writing vs programming line up so perfectly with the RescueTime data. I am very curious to learn/think more about why the 2 activities are stereotypically (and empirically) on opposite schedules. Personally, when writing prose (mostly docs, blog posts, and product plans), I prefer to wake up early and do it in the morning. I much prefer coding at night. My hunch is that this is because interruptions are rarer at night and more bothersome when coding. For anyone else who is both a writer and coder: do you follow the same schedule for both?
同类还值得读
被低估的工程技能：把文章写好
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 条写作要点编辑精选