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

    写作方法2012blog.teamtreehouse.com编辑精选

    我如何在三天内写成一本书

    How I Wrote a Book in 3 Days

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

    导读

    这篇帖子讲作者声称三天写完一本书,引发 HN 读者讨论:快速写作是否牺牲质量、书作为直接消费品为何更需要打磨,以及长期调研和修订的价值。对写作者来说,它值得用来反思“快写”与“写好”的区别,避免把速度当成成果。

    关键词 写作速度书稿打磨读者视角迭代修订

    可以直接用的写作要点

    1. 01

      三天写完可以当作草稿或实验,但不要把速度当成质量,读者直接消费的是文字本身。

    2. 02

      复杂主题往往需要长期调研和多轮修订,初稿之外的打磨时间可能远超三天。

    3. 03

      写作前先明确目的:若只是练习或快速产出,可压缩周期;若追求影响力,就要给打磨留时间。

    4. 04

      少用“伟大产品是决策的结果”这类正确但空洞的格言,多写具体、有信息量的内容。

    HN 评论精选

    软件可以靠成品藏拙,书却直接暴露文字质量,快写更容易显得粗糙。

    当然,没读之前我不会下最终判断。但看到标题的第一反应是一个词:“Poorly”(写得很糟)。不是说这有什么不对。我见过的三天写出来、还有点功能的程序也都写得很糟,但没关系,因为你不消费代码,你消费应用。书的问题在于你直接消费书的产物,所以我怀疑。

    shadowfiend查看英文原文

    I will not pass final judgement on the book until I've had an opportunity to read it, of course. But my initial reaction to this title is one word: “Poorly.” Not that there's anything wrong with that. Every application I've seen that was written in three days with any amount of functionality was also written poorly. But it didn't matter. Because you don't consume the application's code, you consume the application. The trouble with writing a book is that you do consume the product of the book directly. That's why I'm skeptical. That said, maybe this book is awesome. That would be awesome, and hopefully would get more people riding the writing train and flexing that language muscle so many often forget about.

    复杂写作依赖长期调研与多轮修订,三天很难保证深度和质量。

    我写科幻小说,涉及经济、期货市场、基因提升、AI、金融、战斗和轨道力学,每天写3到5小时,写了18个月,对三天能完成的东西不太以为然。我怀疑光研究月球地质、矿物学、钛精炼、空气压缩性就花了不止三天。更别说我的初稿花了9个月,修订花了12个月。有些东西需要迭代和打磨,写作我认为就是其中之一。

    tjic查看英文原文

    Having been working on a science fiction novel that covers economics, futures markets, genetic uplift, AI, finance, combat, and orbital mechanics, and having been working on it for 3-5 hours per day for 18 months ( http://morlockpublishing.com/the-book/ ), I'm somewhat underwhelmed with anything that can be done in three days. I suspect that I spent more than three days on researching lunar geology, minerology, titanium refining, the compresibility of air, etc. Not to mention that my first draft took 9 months, and my revisions have taken 12 months. Some things require iteration and polishing. Writing, IMO, is one of those things.

    速度不是价值,书应追求影响力和质量,别把“快写”本身当卖点。

    我不明白这类文章的要点是什么。很多人用类似公式匆忙传达信息:大学生在学期最后一周写,叫论文;博主一直写,叫博客。书通常意味着深思熟虑、高质量。不是说不能三天写出一本像样的书,但意义何在?很可能让自己处于劣势。重要的是书的影响力。如果三天写完很快被遗忘,而别人花一年打磨出有意义的东西,谁在为读者创造价值很明显。这类文章像“看我三天写了本书”,没提真正独特或需要技巧的地方。我觉得它在鼓励制造人工、一周后就被遗忘的东西。

    moocow01查看英文原文

    I honestly dont understand what the take away is from these articles... Lots of people communicate information in a hurried manner using a similar formula. - College students do it the last week of every semester but its called a paper - Bloggers do it all the time but its called a blog A book typically infers to most people something that has been written in a very thoughtful or high quality manner with much thought put into it (and we have many descriptors for the "lesser" forms... articles, stories, etc.) That doesnt mean you can't write a proper book in 3 days... but whats the point? - you are just likely putting yourself at a disadvantage. What matters is how impactful the book is. If you spend 3 days and its forgotten (sorry but likely based upon effort) and somebody else spends 1 year to craft something meaningful (much more likely based upon the history of literature) its pretty obvious who is creating value for their readers. These articles read to me like "hey look at me I wrote a book in 3 days"... there is no mention of what is truly unique or skillful about it. Sorry to be so negative but I just feel like this encourages the creation of pretty artificial stuff that will be forgotten in a week.

    避免正确但空洞的格言,写作要提供具体信息而非套话。

    “伟大产品只是沿途一系列决策的结果。”烂产品、平庸产品也是。那又怎样?这句摘录没告诉我任何有用的东西。产品都是决策的结果。这种陈词滥调是否代表书的内容?

    jamesbritt查看英文原文

    "Great products are simply the result of decisions made aong the way." So are shitty products. So are mediocre products. So what? That pull-quote tells me nothing useful. Products are the result of decisions. Is this kind of trite observation indicative of the book's content?

    同类还值得读

    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

    关注向阳乔木

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

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

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