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 生成,可能有误。

    写作方法2020snir.dev编辑精选

    书面沟通是远程工作的超级能力

    Written communication is remote work super power

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

    导读

    这篇文章讨论远程工作中书面沟通的价值,评论区则补充了异步与同步沟通的适用场景,并提醒读者:备忘录、结论先行、结构化命令格式等书面沟通传统早已有之。对写作者来说,这既是一份实用沟通指南,也是一次关于“写作即思考”的提醒。

    关键词 书面沟通异步协作写作即思考结论先行

    可以直接用的写作要点

    1. 01

      写作即思考:如果没想清楚要传达什么,既写不出来也说不清楚,所以动笔本身就是整理思路的过程。

    2. 02

      书面沟通默认留下可保存、可检索的记录,这是它相对口头沟通的最大优势。

    3. 03

      会议要有议程,会后要产出书面记录,这是把异步和同步沟通有效结合的关键。

    4. 04

      借鉴“结论先行”(bottom line up front)和结构化格式,能显著提升书面沟通的效率。

    HN 评论精选

    异步沟通适合明确问题,定义不清的问题更适合实时讨论;会议要有议程和记录。

    异步沟通适合解决某些问题,但有两个缺点:参与者需要具备读写文章的能力(这比听起来难),而且即使再小心,想法也容易被误解,从而浪费一个异步周期。对于定义不清、需要做大量决定的问题,尤其是决定趋于武断时,把大家聚在一起讨论要容易得多。会议的问题在于准备不足;应该有议程,并产出适当的会议记录。对于复杂事项,行动和调查应被跟进——某种程度上,这就是把异步和同步沟通结合起来的方式。

    jackjeff查看英文原文

    Async communication is suitable to resolve some kind of issues. But it has two drawbacks: participants need to be competent at writing and reading prose (it’s harder than it sounds) and even with the best of care your ideas can easily be misinterpreted resulting in the loss of an async cycle. For problems which are not well defined, and where a lot of decisions need to be taken, especially when they verge toward the arbitrary, it’s a lot easier to have people in a room and hash it out. A remote meeting can work too. The problem with meetings are those which are not well prepared. There shall be an agenda and proper minutes should be produced. For most complicated matters actions/investigations are supposed to be followed up. In a way that’s how you mix async with sync communication.

    高不确定性、需要探索时口头讨论更高效,但会后要补书面输出。

    实时口头沟通是现场工作的超能力。当不确定性高、需要激烈讨论时,口头表达效率高得多。人们本质上更擅长快速说话和有序轮换发言,而在视频通话、电话或文字聊天中,这种顺序感和轮换协议容易断裂(除非有主持人强制,但会牺牲速度),沟通变得缓慢、低效、令人疲惫。我喜欢逻辑清晰、组织良好的文章,但要写出这样的文章,它回答的很多问题应该已经被理解、回答并安排好顺序——而有些情况下,找出问题的范围与结构本身就是任务,这时面对面口头沟通占优。当然,会后提供书面产出也很重要,可以是在大屏幕上共享的文档,或者只是白板照片。所以书面和面对面沟通都重要,没有哪个能高效替代另一个。

    nine_k查看英文原文

    Real-time, spoken communication is on-site work super power. When uncertainty is high, and an intense discussion is needed, spoken word is much more efficient, from my experience. People are fundamentally better at speaking quickly and taking proper turns. This all is much slower and more cumbersome in video call, phone call, or a text chat. The perceived sequence breaks, the turn-taking protocol breaks (unless enforced by a moderator, at the expense of speed), and the communication become slower, less efficient, and more tiresome. I love neatly written logically organized texts. But to produce such a text, a lot of the questions it answers should be already understood, answered, and arranged in a easy-to-consume order. There are situations when this is not possible, and finding out the scope of the problem and its structure is exactly the task. Here's where face-to-face verbal communication rules. Of course, providing some written output after such a meeting is important, too, be it nicely written minutiae (a shared document on a large screen works well), or just a photo of the whiteboard. So, both written and face-to-face types of communication are important. None can efficiently replace the other.

    文本便于保存检索;写作即思考,没想清楚就说不好,文本质量未必不如口头沟通。

    细想一下,文本是我最喜欢的沟通方式,工作和严肃的私事都是如此。文本的最大优势是它默认提供了历史记录——你可以保存它,也更容易搜索。围绕写作和沟通的心智模型,是投入其中的思维过程,这也是我不同意“你应该擅长写作”这种说法的原因——如果你没思考过想沟通什么,你既写不出来也说不出来。为什么你说得会比写得好?说话或视频更快,但那能带来更好的结果吗?我认为绝对不会。

    danielovichdk查看英文原文

    Actually funny this question. Because come to think about it, text is by far my preffered way to communicate. That goes for work and for serious-private matters. The absolute strengt with text is that it gives you history by default - you can save it. While you can save text it's also eaiser to the search. The mental model around writing and communicating is the mental proces that goes into it, and which is also the reason i disagree with people that believe you should be good at writing - if you haven't thought about what you want to communicate you can't write it nor speak about it. Why would you be better at communicating by speech rather than text? Sure it's faster to speak or video, but does that give a better result? I say no way

    书面沟通有历史先例(备忘录、军事格式);结论先行和结构化格式值得学习。

    这家伙是不是刚重新发明了备忘录?这里有几百年的历史。军队在书面沟通设计上投入很大,有经典的5段式作战命令格式,也有用于信息而非命令的“结论先行”风格,并且严格区分信息文件和命令。外交官也有传统格式,多数信件是正式的,有时会附一份“形势评估”——非正式地总结作者观察到的情况以及他们认为将会发生什么。还有一本有趣的书《如何作为高管生活》(1953年),名义作者是L. Ron Hubbard,实际由Richard DeMille所写,相当于在计算机出现前试图发明Slack:用墙板、夹子、复写纸表格、撕下的票据和专职“沟通员”来运转,但从未被采用,因为前计算机时代太复杂。它的基本概念是问题工单,以及一套有组织的系统,确保把问题交给别人后不会在跟进中丢失。

    Animats查看英文原文

    Did this guy just re-invent memos? There's a lot of history here, going back centuries. The military has put much effort into designing written communication. There's the classic 5-paragraph operations order format. There's the "bottom line up front" style, which for information rather than orders. The military makes a very strong distinction between info documents and orders. Diplomats have some traditional formats, too.[1] Most correspondence is formal. Sometimes there's an "appreciation of the situation" attached to correspondence from a mission to its state department. That's an informally written summary of what the writer has observed and what they think is going to happen. An amusing read is "How to Live though an Executive", which is nominally by L. Ron Hubbard, the Scientology guy, but was really written by Richard DeMille. This is from 1953. It's someone trying to invent Slack, before computers. It's done with wallboards, clips, carbon paper forms, tear-off tickets, and people called "communicators" doing the paperwork. It was never used. Too complicated pre-computer. The basic concept is a trouble ticket, with an organized system to insure that handing off the problem to someone doesn't mean it gets lost to follow-up. [1] https://projects.iq.harvard.edu/files/hks-communications-program/files/pp_sri_kulkarni_and_yotam_goren_4_10_17.pdf

    同类还值得读

    1. 被低估的工程技能:把文章写好

      Undervalued Engineering Skills: Writing Well

      这篇文章讨论为什么“写得好”是被低估的工程能力,以及它如何在团队协作、系统设计和职业发展中持续带来回报。

      写作方法2019 · 1,109 分 · 371 评4 条写作要点编辑精选
    2. 每行只写一句话:让写作和修改都更轻松的排版法

      Writing one sentence per line

      这是 Derek Sivers 的一篇短文,主张写作时每行只放一个句子,而不是按段落排版。

      写作方法2022 · 849 分 · 297 评4 条写作要点编辑精选
    3. 如何写出有用的文字

      How to Write Usefully

      保罗·格雷厄姆在这篇文章里给"有用的写作"下了一个可操作的公式:有用≈重要×新颖×正确×清楚,任一项为零,整篇文章就等于零;他还主张敢下确定判断、删掉让自己心虚的句子。

      写作方法2020 · 821 分 · 285 评4 条写作要点编辑精选
    4. 如何写得更清楚、想得更清楚,并学会复杂材料(PDF)

      How to write more clearly, think more clearly, and learn complex material [pdf]

      这份 PDF 讨论如何把文章写清楚、把思路理清楚,并用写作来学习复杂材料。

      写作方法2022 · 779 分 · 153 评4 条写作要点编辑精选
    5. 用纯文本文件写作

      Write plain text files

      这篇文章主张用纯文本文件写作:不依赖任何特定软件,几十年后依然能打开,还能借助 git 之类的工具记录全部修改历史。

      写作方法2022 · 739 分 · 412 评4 条写作要点编辑精选

    打赏支持

    打赏二维码

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

    WeChat

    关注向阳乔木

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

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

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