HN 写作课

工程师们二十年里聊过的写作。

工程师、作家、编辑和创业者在 Hacker News 上聊了二十年“怎么写”:怎么写得清楚、怎么讲好一个故事、技术文档怎么写、小说和出版是怎么回事。这里把其中关于写作与讲故事的帖子挑出来,配上中文导读、可以直接用的写作要点和评论翻译。

从必读开始
  • 2,600+篇关于写作的 HN 讨论

Writing tips

写作锦囊

正在抽一条写作要点…

Essential

必读 30 篇

在讨论库里看全部精选

编辑精选里 HN 讨论最热的 30 篇,每篇都有中文导读和写作要点。

  1. 正在载入…

Archive

讨论库

按发帖年份分布,点柱子筛选。

排序

    About

    这些讨论是怎么挑出来的

    1. 01

      从全量里捞

      读取 Hacker News 自 2006 年以来的全部帖子,用关键词先捞出 40 分以上、可能和写作有关的约 1.1 万篇。

    2. 02

      只留真正讲写作的

      由 AI 逐条判断是否和写作、讲故事、文风、出版有实质关系,剔除“写代码”“编辑器”这类字面撞车,并分进十个类别。

    3. 03

      提炼可用的要点

      为值得读的帖子写中文导读,提炼 2-4 条可以直接用到自己写作里的要点,并精选翻译 HN 高赞评论。内容由 AI 生成,可能有误。

    写作与思考2017msutoday.msu.edu

    表达性写作能降低压力任务下的大脑负荷

    Expressive Writing Cools Brain on Stressful Tasks

    阅读原文 HN 讨论
    151HN 得分
    49条评论
    4条写作要点

    导读

    这篇报道介绍一项研究:在压力任务前进行表达性写作,能帮助大脑“降温”,降低焦虑、释放认知资源。对写作者来说,重点不只是写得好,而是把写作当成调节情绪、整理思路和推进工作的工具。读它可以帮助你理解为什么“先写几句”往往能让人更快回到正事。

    关键词 表达性写作压力管理写作方法思维整理

    可以直接用的写作要点

    1. 01

      面对压力任务时,先花几分钟写下自己的担心、待办和卡点,再开始做事,能减少脑子里的反复占用。

    2. 02

      把混乱进展写成固定栏目的短记录(已完成/待推进/暂存),既方便别人读,也逼自己把状态想清楚。

    3. 03

      不要只把写作当成品输出;手写笔记、私人草稿、给自己看的复盘,都是低成本的思维整理。

    4. 04

      写作时允许自己写得坦诚甚至粗糙,先释放情绪、留下线索,再回头提炼成可读文本。

    HN 评论精选

    结构化写作能把项目状态外化,提升可见性和执行。

    我们曾要求软件开发者按三类写进展:已完成、待推进、留待以后,像个人看板,用来共享每周交付进度。文字必须认真写、负责人必须读,不能最后赶工;“留待以后”帮助团队保持时间盒和同步,也给管理者提供未来版本排期素材。作者称这套做法让 125 个项目全部完成。

    Chiba-City查看英文原文

    We used (enforced) a writing method for software developers of three categories: So Far, More To Go, Save It For Later. It was something like a personal Kanban board for project members sharing a real schedule in weekly compiled/tested feature deliveries. This was a visibility feature for schedule and release rationalization. There were no Hail Mary pass negotiations or requests permitted. The prose mattered and project leads were forced to read them. It was not anything that could be rushed at the end. "Save it for later" kept team time boxed and synchronized and gave managers features to schedule for future version releases and sales messaging. We fired people who could not write English right alongside their Java and PL/SQL. It worked great. 100% project completion over 125 projects. I attribute it to HR weeding out ADHD gamers suffering bad grammar of inadequate educations needing paychecks. Software is 100% a product of communicative action. There are few excuses for execution failure absent bonafide academic grand challenges.

    写作(包括手写笔记)是整理思路和缓解压力的工具。

    我喜欢文学化编程,部分原因就是它带来这篇文章所说的好处。即使文档和程序分开,有时逃进写作里一会儿,就足够缓解压力,让我能重新回到编程。因为写的内容和手头任务相关,它还能帮我整理思路,让我更好地准备、也因此更少压力地重新面对问题。我也用手写笔记:完全离开屏幕,随意而坦诚地写,自然把压力改造成可处理的东西。

    mikegerwitz查看英文原文

    I enjoy literate programming in part for some of the benefits this article describes. Even if the documentation is separate from the program, sometimes escaping into writing for a while provides a sufficient amount of relief to just get back into hacking. Since the matter is related to the task at hand, it also helps me to organize my thoughts and be better prepared (and therefore less stressed) to re-introduce myself to the problem. I also use hand-written notes. This allows me to escape a screen entirely, write candidly about whatever I please, and naturally reform the stress into something workable.

    坦诚甚至粗粝的私人写作能释放情绪,并留下可回看的“卡点记录”。

    我发现卡得很惨时,在提交信息里写几句脏话有帮助:它让我停止反复想这个问题,第二天回来还能从记录看出当时卡在哪。当然只适合不分享的仓库;共享仓库要小心,别把草稿推上去。

    chicago_wade查看英文原文

    I have also found that it helps to put swear-words in the commit messages when I'm struggeling a lot with something. Once I get to that point I will stop working on that specific problem until the next day, but swearing about it in the commit message helps me not think about it anymore and also when I come back to it the next day I can see from the commit what I was struggeling with. Obviously only do this for repositories that you aren't sharing with anyone. You could also do it in a shared repo if you don't push the commits and you squash them first. Personally I'm not a squash kind of person and I'd also fear that I pushed without remembering to squash even if I really were planning on squashing.

    把任务外部化到清单或收件箱,能减轻记忆负担和压力。

    这项研究印证了 GTD 书里的说法:把所有任务放进一个“收件箱”能减轻压力——这是我从那本书里得到的唯一有价值的洞见。

    copperx查看英文原文

    This study gives credence to the GTD's book claim that putting all of your tasks in an "inbox" reduces stress, which was the only worthwhile insight I got from it.

    同类还值得读

    1. 不要想好再写,要写来思考

      Don’t think to write, write to think

      这篇短文主张不要把写作当成思考完成后的记录,而要把写作本身当作思考的工具:动笔的过程会逼出想不清楚的地方。

      写作与思考2022 · 553 分 · 145 评4 条写作要点编辑精选
    2. 写作即思考:学会自信地写作

      Writing Is Thinking: Learning to Write with Confidence

      这是一篇讲“写作即思考”的博客:作者认为写作不是把想好的东西誊写出来,而是借助写作本身把想法想清楚,因此写作者应当建立信心、敢于先写烂稿。

      写作与思考2019 · 529 分 · 83 评4 条写作要点编辑精选
    3. 如何用写作来思考

      How to think in writing

      这篇文章讨论的是「用写作来思考」:作者认为写作不只是把想清楚的东西表达出来,更是想清楚本身的工具——文字落在纸上,你才有机会看见自己思路里的跳跃、含混和漏洞。

      写作与思考2024 · 424 分 · 120 评4 条写作要点编辑精选
    4. 写作,帮你逃离默认的人生设置

      Write to Escape Your Default Setting

      文章的核心主张就写在标题里:写作是帮你逃离「默认设置」的手段——日常的思维和表达都有惯性默认的默认模式,而落笔能逼你跳出来,重新看清自己到底在想什么、要说什么。

      写作与思考2025 · 407 分 · 93 评4 条写作要点编辑精选
    5. 写作就是思考

      Writing is thinking

      文章以“写作即思考”为题,讨论写作不只是把已有想法记录下来,而是帮助澄清、组织和推进思考的过程。

      写作与思考2025 · 330 分 · 128 评4 条写作要点编辑精选

    打赏支持

    打赏二维码

    觉得有用,请作者喝杯咖啡。

    WeChat

    关注向阳乔木

    微信公众号「向阳乔木推荐看」

    微信公众号「向阳乔木推荐看」二维码

    微信扫一扫;在微信里打开本页时,长按二维码识别。