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

    写作方法2020blog.griffin.sh编辑精选

    我们如何写作

    How We Write

    阅读原文 HN 讨论
    71HN 得分
    24条评论
    5条写作要点

    导读

    这是一篇公司写作指南:团队公开自己推崇的写作风格,主张用平实的词替换术语和“商务腔”,语言要清晰、诚实、直接。对写作者来说,它提供了一个具体的文风自查清单;评论区的讨论则进一步谈到个人声音与公司语气的张力、朗读校对的效用,以及奥威尔式的清晰英语原则。

    关键词 写作风格清晰表达编辑校对企业文风

    可以直接用的写作要点

    1. 01

      把“商务腔”和术语换成日常用词,避免为了显得专业而制造距离感。

    2. 02

      定稿后换一个介质朗读出来(打印,或改字号、字体),靠听觉发现眼睛漏掉的错误。

    3. 03

      让文字保有自己的个性,即便是在代表公司发言时,也不必把个人声音完全抹掉。

    4. 04

      采用短段落、短句,必要时把“你”换成“我/我们”,减少命令式的压迫感。

    5. 05

      把编辑当成持续过程:发表后仍可修正错字、链接,补上勘误和补充信息。

    HN 评论精选

    换介质并朗读,是发现写作错误的高效自查法。

    几年前别人给我的一个建议彻底改变了我的写作:文档写完后打印出来(或换到别的设备、换个字体),然后出声读一遍。把文字换到另一个环境和介质(语音)后,你几天都没发现的错误会突然变得非常明显。这花不了多少时间,而且听到自己的文字时感知方式不同,质量会提高,我可以把这种感觉带回最终修改。

    slashink查看英文原文

    The tip that someone gave me a couple of years back that has changed my writing is to once the document is finished, print it (or transfer to another shaped device/change the font) and read it out loud for yourself. Transferring the writing to another environment and medium (speech), errors that you've missed for days suddenly become very obvious. Doesn't take that much time and the quality of the writing goes up when hearing the prose as I perceive it differently, which allows me to feed this back into the final edit.

    警惕企业语气指南抹平个人声音,文风应当属于写作者自己。

    我理解写作规范的价值,但公司为员工制定“语气指南”让我不太舒服。我不是说它一定错,也不是说它没用,只是这像是又一小步在抹去员工的个体性。我遵循并喜欢给出的建议是:写作风格应体现你的个性,即使在见客户、面对媒体或内部沟通时,你的个体性也该在某个层面存在。文风应属于你,而不是属于公司;例外是专职发言人,或起草公司立场文件的律师,但那与这份指南的用途完全不同。它说“我们如何写作”“我们的声音就是我们”“我们清晰/诚实/透明”“我们赋权他人”,看着实在像博格人。补充一点:它说“把正式词换成普通词,英国‘商务腔’里有一整套词能让你听起来专业,但也显得不必要地疏远,我们尽量避开”,这让我想起另一种文化变化,原则其实没变,就像“还记得人人都得穿西装、谁穿件素T恤来上班就被取笑的日子吗……”。

    soneca查看英文原文

    Ok, I understand the value of writing, but it feels uncomfortable to me that a company creates a "Tone of Voice guide" for its employees. I am not saying that is necessarily wrong (maybe it is), nor that is not useful, but it just seems like another small step in removing the individuality of the people working there. It doesn't feel right to me. The writing advice that I follow and that I like to give is that your writing style should reflect your personality. Your individuality should be with you on some level even if you are representing your company in a meeting with a client, or to the press, or internally. Writing style should be unique to you, not to your company. An exception should be someone whose job is to be the spokesperson or a lawyer creating a document that declares the position of the company. But that's a very different use case from the one declared at this guide. The way it says "How we write", "Our voice is who we are", "We are clear/honest/transparent", "We are empowering"; it looks uncannily familiar to the Borg. eidt: Another thing. When they say "Swap formal words for normal ones. There's a whole lexicon of British "business-speak" that one can use to sound professional, but also needlessly distant. We try to avoid that: It reminds of another cultural change where the principles remained just the same, like: "Remember when everybody on business had to wear a suit and people would make fun of anyone who showed to work on a plain t-shirt? We are not like that. Here we make fun of people who want to wear a suit".

    奥威尔六规则与《Plain Words》是练习简洁英语的经典范本。

    两本关于清晰、不矫饰英语的宝贵指南,一短一长:乔治·奥威尔的文章《政治与英语》,其中有他著名的六条写作规则;欧内斯特·高尔斯爵士的《Plain Words 大全》,最初是为以冗长著称的英国公务员系统写的文体指南,他在书中举了古埃及财政部的一份备忘录作为典范:“阿波罗尼乌斯致芝诺,问候。你把鹰嘴豆送到孟菲斯,做得对。再会。”

    dghf查看英文原文

    Two invaluable guides to clear, unfussy English, one short and one long: * George Orwell's essay 'Politics and the English Language' [0], which includes his six rules for writing * Sir Ernest Gowers' The Complete Plain Words [1], originally a style guide for the notoriously prolix British Civil Service, in which he offers this memo from the ancient Egyptian ministry of finance as a paragon: > Appollonius to Zeno, greeting. You did right to send the chickpeas to Memphis. Farewell. [0] https://www.orwell.ru/library/essays/politics/english/e_polit [1] https://en.wikipedia.org/wiki/The_Complete_Plain_Words

    用短段落、把“你”换成“我/我们”、发表后持续编辑,能让文字更亲和。

    我很喜欢这篇,也喜欢他们那篇《Making Decisions》。我知道这基本是宣传材料,但写得很有格调。我觉得对自己来说一个好练习是做类似的事。我尽量用口语化、贴近日常的语言写作;把技术文档写成催眠药让我难受。在日本公司工作时,我养成了把文字切成小段、常常一句话一段的习惯。我最近还开始做一个练习:把“你”换成“我”或“我们”,因为我发现人们对命令式语气反应偏负面。对我来说编辑是持续过程,文章发布后我还会不断修改,有时几周后才发现错字或可疑语法;我也常继续查证,改链接,或补上事后的更新、勘误和说明。

    ChrisMarshallNY查看英文原文

    I enjoyed that! I also enjoyed this: https://blog.griffin.sh/2020/04/17/making-decisions/ I know it’s basically promotional material, but it’s pretty classy stuff. I wouldn’t mind if most corporations did the same. I think a good exercise for me would be to do something similar. I do have this, but it is not really the same kind of thing: https://medium.com/chrismarshallny/leaving-a-legacy-1c2ddb0c8014 I try to have a casual voice in the vernacular. It pains me to use technical documentation as a soporific. I got used to breaking up my writing into small paragraphs; often single sentences, when I worked for a Japanese company. Another exercise that I have started doing in my writing, is to exchange the word “you” with “I” or “we.” I have found that people tend to react a bit negatively to a dictatorial tone. Editing, for me, is a kind of ongoing process, and I will revise a document continuously after publication; sometimes, finding typos or suspect grammar weeks later. I often continue to fact-check, and will do things like correct links, or add “after the fact” updates with additional information, errata, or elucidation.

    同类还值得读

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

      Undervalued Engineering Skills: Writing Well

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

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

      Writing one sentence per line

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

      写作方法2022 · 849 分 · 297 评4 条写作要点编辑精选
    3. 书面沟通是远程工作的超级能力

      Written communication is remote work super power

      这篇文章讨论远程工作中书面沟通的价值,评论区则补充了异步与同步沟通的适用场景,并提醒读者:备忘录、结论先行、结构化命令格式等书面沟通传统早已有之。

      写作方法2020 · 831 分 · 190 评4 条写作要点编辑精选
    4. 如何写出有用的文字

      How to Write Usefully

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

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

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

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

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

    打赏支持

    打赏二维码

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

    WeChat

    关注向阳乔木

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

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

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