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

    写作方法2019lithub.com编辑精选

    悄悄潜入你文章里的坏习惯

    Bad Habits Creeping into Your Writing?

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

    导读

    这篇文章提醒写作者留意一些不易察觉的坏习惯,比如把口语习惯带进书面语、滥用代词、开头迟迟不进入正题、初稿用词冗余。它值得写作者读,因为每条都能落实到具体修改动作,帮助文章更清楚、更紧凑。

    关键词 写作习惯精简表达代词指代书面语

    可以直接用的写作要点

    1. 01

      开头第一段就让读者知道文章要讲什么;写作前的“热身”只用于自己找思路,定稿前应删掉。

    2. 02

      初稿常含大量可有可无的词句,做一次以“删尽冗余”为目标的修改。

    3. 03

      书面语不是口语:同一句甚至同一段里避免用同一个代词指代两个人,防止指代混乱。

    4. 04

      短名称或短语不必急着用缩写;数据报告中适度重复关键信息反而有助理解。

    HN 评论精选

    开头热身和冗余词句应删掉,第一段要直入主题。

    我对非虚构作品(尤其是博客)最受不了的,是作者在进入正题前冗长的热身。写作时不知道要说什么、甚至焦虑,先写点东西帮自己找到思路,这本身没问题;问题是把这些废话留在文章里。删掉它!如果我读第一段还不明白接下来要读什么,多半就不读了。另一个不喜欢的是用词太多:初稿的明显标志就是大量不必要的词甚至整句。做一次狠心删掉每个不必要词语的编辑,对任何初稿都很有奇效。

    apo查看英文原文

    My own pet peeve in non-fiction, particularly the kind that appears on blogs: the excruciating warmup before the author finally gets to the point of the post. I know why this happens. When you sit down to write, you don't know what exactly you're going to say. You may even be anxious about it. Then, an idea sparks your imagination and you start writing stuff. The warmup that comes out initially gets you on track. Nothing wrong with that. The harm is keeping that crap in the post. Delete it! If I don't understand what I'm about to read in the first paragraph, I'm probably done. Something else I don't like: writers who use too many words. The telltale sign of a first draft is the vast quantity of words (and even entire sentences) that don't need to be there. A single edit with the goal of ruthlessly eliminating every unnecessary word works wonders for any first draft. Edit: On the topic of fiction, the author gives a beautiful example from the Wizard of Oz: > When Dorothy stood in the doorway and looked around, she could see nothin but the great gray prairie on every side. Not a tree nor a house broke the broad sweep of flat country that reached the edge of the sky in all directions. The sun had baked the plowed land into a gray mass, with little cracks running through it. Even the grass was not green, for the sun had burned the tops of the long blades until they were the same gray color to be seen everywhere. Once the house had been painted, but the sun blistered the paint and the rains washed it away, and now the house was as dull and gray as everything else. [continues] I haven't read the book but this passage alone makes me want to.

    书面语要避免代词指代混乱,写作不等于口语。

    文章说许多写作者过度依赖代词。写作不是说话:口语里一连串“他/她”通常还能听懂,落到纸面就容易混淆。强烈建议同一句里不要用同一个代词指两个人,甚至同一段也避免;写同性恋爱小说的作者常为此头疼。

    Animats查看英文原文

    From the article: Many writers rely more heavily on pronouns than I’d suggest is useful. For me this sort of thing comes under the heading Remember that Writing Is Not Speaking. When we talk, we can usually make ourselves understood even amid a flood of vague “he”s and “she”s. On the page, too many pronouns are apt to be confounding. I’d strongly suggest to the point of insistence that you avoid referring to two people by the same pronoun over the course of a single sentence; to be frank, I’d suggest that you avoid it over the course of a single paragraph. (I know a few authors of same-sex romance novels who are regularly driven to tears by this sort of thing.) Tightened up: Pronouns can be overused. Writing is not speaking. When we talk, we can understand who's who amid a flood of "he"s and "she"s. On the page, that's confusing. Best to avoid referring to two people by the same pronoun in the same sentence. (Same-sex romance novelists struggle with this.) Who, besides the guy himself, says this guy is the "Internet's copy editor in chief"?

    数据写作中慎用缩写、允许重复,核心仍是写作不是说话。

    我工作中偶尔要撰写和编辑数据公开报告,只是用英文陈述数据,不猜因果或未来影响。我希望更多人接受“写作不是说话”。除了代词,这条建议还适用于:短名称或短语不要用缩写,“Department of Motor Vehicles”虽长,但看过两次后“DMV”也不见得更省眼;如果文字篇幅看起来吓人,再考虑用缩写。重复没关系,甚至很好:数据尤其需要重复呈现,表格是极致,叙述文字也可行。

    vharuck查看英文原文

    An infrequent part of my job is writing and editing public reports about data. Not even guessing as to causal factors or future impacts, just stating the data in English. I wish more people would accept that writing is not speaking. Beyond pronouns, when this is good advice: - Don't use acronyms for short names or phrases. "Department of Motor Vehicles" is a mouthful, but not much more of an eyeful than "DMV" after seeing it twice. (Consider using the acronym if the amount of space filled with text looks daunting). - It's okay to be repetitive. In fact, it's good to repetitively present data. The pinnacles of this is the table, but narrative text also works.

    警惕“that said/that being said”这类陈词滥调。

    Hacker News 评论和技术博客也该有类似版本。每次看到“that said”或“that being said”我都会不自觉皱眉。

    coat查看英文原文

    There should be a version of this for hacker news comments and tech blog posts. Every time I see the phrase 'that said' or 'that being said' I involuntarily cringe. https://hn.algolia.com/?sort=byDate&prefix&page=0&dateRange=all&type=comment&query=%22that%20being%20said%22

    同类还值得读

    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

    关注向阳乔木

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

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

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