写作方法2022davnicwil.com编辑精选
让写作变得更有趣的几个技巧
Tips for making writing more fun
导读
这篇短文讨论的是如何让写作（尤其是博客和技术文档）重新变得有趣：不要把文章当成待办事项拖着，不要过度打磨，读者也不会像作者那样逐字细读。对写作者来说，它提供的是一组“降低启动门槛、尽快发布”的实用心态，评论里还补充了大量职业写作者的具体工作法。
可以直接用的写作要点
- 01
用一个真实、自己熟悉的例子贯穿全文（例如一个具体的应用或亲身经历），而不是抽象地罗列概念，文章自然就有故事感。
- 02
与其让草稿躺在文件夹里无限修改，不如把 80% 完成的文章发出去，永远没发表的完美文章比它差得多。
- 03
别为读者过度操心：你反复纠结的细节，绝大多数人根本不会注意；遇到专业术语，直接链到定义比塞一大段解释更省事。
- 04
先想好标题和结尾，让一条主线从开头贯穿到结尾；写不下去的收尾可以干脆停笔发布，但适当地说明内容尚未完整，比硬凑一段更尊重读者。
HN 评论精选
用真实例子、链接和“写完就发”来降低写作摩擦，别把完美当门槛。
一位靠写作吃饭的人补充了几条：把文章写成故事，比如写框架就用一个真实的示例应用；把以前写过的相关内容用链接带出来，既避免跑题的侧栏，也能指向别人的作品；写完就发；记住你纠结的细节读者多半不会在意——想想你自己读文章时有多粗略；先定标题和结论，让主线贯穿；该舍弃的段落就舍弃，再有趣也要挪到另一个文档或直接删掉。
mooreds查看英文原文
Other tips for making writing more fun, from someone who does it for a living (plus some other stuff #devrellife): * make it a story. If you are writing about an application framework, use an example application and make it something real (a todo app, a real estate search app, something you have personal experience with). * link to your other stuff. He has a good point about sidebars (don't do it), but if you have written about something tangential previously, links are a nice way to avoid that. Works for pointing to other people's work as well. * just ship it. He alludes to this in the last point, but seriously, the perfect blog post that never is published is 100% worse than the 80% done blog post. * remember that while you are obsessing over everything, your reader likely isn't. Recall how closely you read this article? That is how closely most readers will read anything you publish. * start with the end in mind (the title and the conclusion should be related and the thread should run through it). * kill your darlings. If something doesn't fit, no matter how interesting or witty it is, copy it off to some other doc (possibly for another article). Or delete it. Either way, remove it from your piece.
把写作拆成“先倾倒、后打磨”两个阶段，并用固定时段和仪式感保护初稿时间。
在亚马逊写了两年文档、累计上千页之后，我的做法是：趁早上脑子清醒、没被会议耗干时写；留出两三个小时；咖啡加空腹；先一口气倾倒出初稿，细节留一堆“待补”；先用纸笔在笔记本上画思路，离开手机和电脑，再去电脑上倾倒；不设字数目标，写多少算多少；前期不排版、不校对；洗个热水澡有助于理清思路；脑子烧干了就出去走走，回来再接着写。
amznbyebyebye查看英文原文
After two years of doc writing at amazon, probably Over 1000 pages of content at this point- Early in the morning, when mind is fresh, not after full day of meetings Block off 2-3 hours Caffeine, empty stomach- Start with first draft and just brain dump. Don’t worry about details.. leave lots of <<fill this in later>> Start in a notebook with pen and paper only, physically remove yourself from phone and computer, sketch your thoughts on paper and then go to computer to brain dump Don’t aim for any amount.. no doc is too little Don’t format, proof read, correct too much at the beginning Little wine/beer/whiskey can help (but you probably don’t want to do this early in the morning) Long Hot shower can help you gather your thoughts Take a break when your brain is fried, walk around, come back to it fresh
用链接代替冗长的行内解释；发布未完成内容时加一句说明反而是尊重读者。
关于“假设读者懂基础、不懂会自己去查”：遇到技术术语时，直接链到相关定义是个很好的折中，既省去在正文里塞一段解释的别扭，也省去读者多次点击查找的麻烦——链接正是互联网的美妙之处。至于“没写完就直接发”，我同意，但这其实是前面“别加免责声明、直接说”的一个例外：说明内容尚不完整往往更好，因为这样更尊重读者。
devadvance查看英文原文
> Assume readers know the basics or will look them up [...] One of the beautiful things about reading on the internet is that google is just a click away. Especially in the case of technical jargon, it's a good middle ground to link to a relevant definition directly. That avoids the friction of a suboptimal in-line definition and the friction of forcing a multi-click lookup. A beautiful part of the internet is links :). > Instead of leaving posts as a boring todo chore in the drafts folder, it's perfectly fine to just stop cold and publish if a wrap up doesn't flow naturally. Honestly, nobody cares. While I agree with publishing incomplete content, I would argue that this is an exception to the "Don't caveat, just say it" section from earlier. It's often helpful to caveat incomplete content because it treats the reader with greater respect.
同类还值得读
被低估的工程技能：把文章写好
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 条写作要点编辑精选