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

    出版与作家生涯2015blog.stephenwolfram.com

    我写了一本书来教 Wolfram 语言

    I Wrote a Book to Teach the Wolfram Language

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

    导读

    这篇是 Stephen Wolfram 介绍自己为 Wolfram Language 写入门书。HN 讨论虽多围绕开源与商业生态,但对写作者有启发:技术教学写作若忽略新手动机、把实用成果放到最后,再强大的工具也难以留住读者;同时要避免专家盲点和过度包装。

    关键词 技术写作教学法读者动机克制夸大

    可以直接用的写作要点

    1. 01

      先给读者一个马上能动手、能获得成就感的小目标,再展开系统知识。

    2. 02

      警惕专家盲点:你熟悉的抽象概念和高级功能,对新手可能是劝退门槛。

    3. 03

      少用“只有这个工具才能做到”的暗示,克制夸大,让例子自己说话。

    4. 04

      降低读者的进入门槛和参与成本,教程才更容易被传播和持续使用。

    HN 评论精选

    技术写作应从读者动机和可感成果开始,避免专家盲点。

    他和许多人在学习和教学法上有同样的“专家盲点”。如果拿这本书给真正的新手,比如孩子或完全非程序员看,会让他们很久不想碰编程。要吸引人、给人真正学编程的理由,需要先展示编程能做什么好玩或有用的事,比如做小游戏或帮助处理表格。相反,他把用语言创造有用东西放到书最后。应该从做简单网页或小游戏开始,而不是以此结尾。而且专有工具对新手也是障碍。

    edtechdev查看英文原文

    He has the same 'expert blindspot' as so many others when it comes to learning and pedagogy. If you show this book or go through this book with a true novice, like a child or complete non-programmer (no one has 'zero' knowledge like he says), this would turn them off programming for a long time. To hook people in, to give them an actual /reason/ to learn programming, you need to show them how programming can be used to do something fun or useful. For example making a little game, or making something to help with a spreadsheet or so forth. Instead, he waits until the very end of the book to start thinking about using the language to create something useful: "OK, so now everything is ready to talk about deploying things to the web. And at this point, people will be able to start creating useful, practical pieces of software that they can share with the world." Start with how to make a simple web page, or a simple game that others can play, etc. Don't end with that. Make it easier for people to use your tool to make games or practical applications. Then again, as others have pointed out, the fact that this tool is proprietary though makes it a non-starter for novices, anyway, in my opinion.

    避免把工具能力写成万能神话,克制夸大。

    我不喜欢他总在暗示,像识别猎豹图片这种高级功能,只是因为 Mathematica 语言独特万能才可能。

    maurits查看英文原文

    I really don't like the fact that he is forever hinting that higher level functions, such as recognizing an image of a cheetah, are (only) possible due to the unique omnipotent nature of the mathematica language.

    开放核心、降低参与门槛,才可能让更多人使用并共建;教程写作同理。

    他漏掉了最明显的一点:开源。未来能成功的语言只会是开源的;核心语言和引擎应以 MIT/BSD 等宽松许可开放,才能长出生态。微软、苹果、Scala、Oracle 都在不同程度上这么做了。Mathematica/Wolfram 很棒,但若开源核心,付费用户和贡献者可能多十倍;否则未来科学计算平台会围绕 Python 和 Julia,Wolfram 的工作会被遗忘。

    nnq查看英文原文

    ...if only S. Wolfram would finally have the most obvious insight that he's totally missing: Open-source it! The only programming languages that will ever succeed from now on will be the open source ones. Yeah, he can keep special-purpose libraries closed-source. And the server-software behind Wolfram. Maybe even the Mathematica GUI if he also offers a free "community version" or something on the side. But otherwise this will just not work. But the core language and core engine must be open-source with a liberal MIT or BSD license for it to ever grow an ecosystem around it. Even Microsoft gets it now (with C# and many other stuff)! Apple also gets this with Swift! Typesafe gets it with Scala. Even Oracle partially got it in a twisted way, by allowing things like OpenJDK to exist! Really, Mathematica and Wolfram seem wonderful tools, but probably as many as 10x the number of paying users would start to use them and contribute to their development (and most of them would also pay for "pro versions",trust me), if only they had an open-source core... But it's probably too late and any future scientific computing platform will be built around Python and Julia and all the great work done by Wolfram Software will simply be forgotten because they simply don't grok how "business growth" and "software ecosystems" work in the 21st century...

    同类还值得读

    1. 写书:值得吗?

      Writing a book: is it worth it?

      Martin Kleppmann(《设计数据密集型应用》作者)复盘写书到底值不值:金钱回报低、耗时极长,但带来了可见度、信任和职业机会。

      出版与作家生涯2020 · 642 分 · 287 评4 条写作要点编辑精选
    2. 写书并不是个好主意

      Writing books is not really a good idea

      这篇文章讨论靠写书谋生的现实难度,评论区从版税数学、收入预期和写作目标三个角度补充了作者视角。

      出版与作家生涯2021 · 577 分 · 609 评4 条写作要点编辑精选
    3. 如何自助出版一本书:实用资源清单

      How to self-publish a book: A handy list of resources

      这是一份关于「如何自助出版一本书」的资源清单帖,涵盖从编辑、排版到 ISBN、销售渠道的实操工具与花费。

      出版与作家生涯2018 · 558 分 · 88 评4 条写作要点编辑精选
    4. 我自助出版一本Ruby on Rails书,赚了7万美元

      How I Made $70k Self-Publishing a Book about Ruby on Rails

      这是一篇 Ruby 开发者自述:他把一套 Rails 性能课程(书+视频+答疑)自出版,一年毛收入约 7 万美元,并总结了选题、定价、营销等经验。

      出版与作家生涯2017 · 539 分 · 175 评4 条写作要点编辑精选
    5. 石黑一雄警告年轻作家因“恐惧”而自我审查

      Sir Kazuo Ishiguro warns of young authors self-censoring out of 'fear'

      石黑一雄提醒年轻作者因“恐惧”而自我审查,即这条帖子讨论的核心。

      出版与作家生涯2021 · 396 分 · 641 评5 条写作要点编辑精选

    打赏支持

    打赏二维码

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

    WeChat

    关注向阳乔木

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

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

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