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

    出版与作家生涯2021terathon.com编辑精选

    所以你想写一本技术书

    So you want to write a technical book

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

    导读

    本文是给想写技术书的人的一份实务指南:传统出版流程、合同里的坑、以及自出版的实际收益。正文和评论都指向同一个结论——技术书的读者更在意准确性而非文笔,自出版加上免费版本往往比传统合约更划算。值得写作者读,是因为它把"写什么、写给谁、怎么交付"这三件写作前必须想清楚的事,放在了真实的商业语境里。

    关键词 技术写作自出版出版合同读者反馈

    可以直接用的写作要点

    1. 01

      先分清你要写的是覆盖整个领域的"主题书",还是只深入一个点但写得权威彻底的"话题书":前者可能赚钱,后者主要赚声誉。

    2. 02

      技术书的第一读者群要能在早期真正测试代码、核对正文与代码是否一致、验证步骤是否清晰;这类校对比文字润色更有价值。

    3. 03

      用一个免费的网络版本换取读者规模和真实反馈,再用付费版或增值内容变现,往往比单纯求捐助有效。

    4. 04

      动笔前就明确书的范围与目标读者,范围越清楚,篇幅、结构和你愿意免费给出的部分就越好安排。

    HN 评论精选

    传统出版合同分成低、付款慢、条款陷阱多,自出版回报更高且校对重点应放在技术准确性上。

    传统出版基本是坑:作者说能拿一万美元,但我的大多数书出版商只肯给两千,而且分一两年才付完。他们还会要求"未来所有媒介的全部权利",90 年代到 2000 年代初签下这条款的人,后来失去了最赚钱的电子书和有声书权利。除非你请得起版权法专业律师,否则别签。自出版方面:排版不是问题(Leanpub 转换很好);编程书的文字校对用处不大,读者更在意代码能不能跑、正文和代码是否对得上、说明是否清楚,靠一批早期读者把关更有效。最赚钱的渠道是 Leanpub、Gumroad 这类给 80–90% 分成的平台,亚马逊在定价超过 9.99 美元时只给 30%,而多数技术书都得定在这个价位以上。

    shantnutiwari查看英文原文

    Going via traditional publishing is a fools game. The author says you can get $10,000, but for most my books, publishers would only pay $2000. And even that amount is paid over 1-2 years. And he's right about publishers trying sleazy things. Another thing they may ask for is "All future rights in any medium". So people who signed this clause in 90's/early 2000s lost right of their ebook/audiobooks, which are the most profitable. I would not go with a traditional publisher unless you can afford to hire a lawyer who specialises in copyright law (and not an English lit graduate, which is what most agents are). Self publishing-- from my experience: * Typesetting has never been a problem, but then I write general programming books, and Leanpub handles the conversion really well. * I never found copyediting/proofreading very useful for programming books (though I do use them for my fiction). Readers care more about technical accuracy-- ie, does the code work, does the text and code match. are instructions clear etc. A good set of 1st readers is very useful here. The best way to make money is to sell digital copies via leanpub/gumroad, as these sellers pay 80-90% royalty. Amazon will only pay you 30% if you price your book over $9.99, which let's be honest, most technical books will be. Nathan Barry popularised the formula of selling the book for $39+, and extras for higher pricing, and that works the best.

    区分覆盖领域的主題书与深耕一点的话题书,前者求利后者求名,书本身也可以是一份长期的职业广告。

    我的书通过 Amazon 自助出版,并且把整本书的源码和制作流程公开在 GitHub 上。因为网上有免费的网页版,书本身赚得很少,但我也说不清因此损失了多少销量。有趣的是 GitHub 的数据能告诉你读者对这本书有多感兴趣:我尚未完成的新书仅凭分析数据就显示出更高的关注度。另一个重要区分是"主题书"和"话题书":主题书覆盖整个领域,成了能赚不少钱;话题书只钻一个细节,但写得权威彻底,带来的是声誉而非收入。对我来说,乐趣在于研究和写作、以及有人读;职业上我把它当作为自己技能做的广告,我因此拿到了一家大厂的职位,接外包也容易多了。

    magicloop查看英文原文

    I'm an author of a book also published through Amazon Direct Publishing. I've documented how my book is put together with source code, so if you want to produce something suitable for self-publishing, have a look at: https://github.com/faisalmemon/ios-crash-dump-analysis-book I make very little money on the book itself because I have a free web-based version hosted on GitHub. However, I don't know how many sales I've foregone because of this. Curious thing about it is that the GitHub analytics tells you how interested people are in your book. My in-progress book has much more interest just from the analytics. (The Road to Zero. This book explains how to develop your own zero day vulnerabilities for iOS.) Another thing I think is important is to know the difference between a subject book and a topic book. Subject books provide a wide coverage for a domain. You can make a lot of money if it is a hit. Topic books drill just one detail but authoritatively and comprehensively, so gain you reputation rather than money. For me, the pleasure is in the research and writing of a book, and having people read it. Professionally, I see it as advertising for my skills. I've landed a FANG role as a result and it certainly makes contracting for roles easier.

    传统出版存在隐瞒批发折扣的问题,而免费送书这种营销方式对细分技术书更有效。

    传统出版的猫腻让人震惊,尤其是"高折扣"那一条:很多书商(包括亚马逊)的标准批发折扣是 55%,而出版商当面跟我撒了谎。我一开始就选自出版,因为我写的是 100 页左右的细分领域编程书。我的主要营销策略是经常免费送书,效果比请求打赏好得多。

    asicsp查看英文原文

    Gotchas with traditional publishing is shocking, especially the "Deep discounts" part. >It turns out that a 55% discount was the standard wholesale rate for many booksellers, including Amazon. The publisher lied straight to my face. I started with self publishing since I was writing 100 page niche programming books. My main marketing startegy is giving away books for free often, which turned out to be more effective than asking for donations.

    随意付费的自出版既能扩大读者规模,也能带来收入与反馈,胜过传统出版商的预付加分成条件。

    我在 Leanpub 上用"随意付费"模式出版了一本 Go 书和一本 Python 书。比起顶级出版商给我的条件,这种方式带来的收入和满足感都高得多,流量也来自自然搜索和 Reddit 发帖。那家出版商只肯给 4 万卢比预付,再加卖出一千册后的分成。对比之下,我的 Go 书有几千人下载,多数是免费下载,也有人付了钱,是双赢。有几千人下载我的书,对我来说意义重大,还收到过几封很好的邮件反馈。所以整体上我很喜欢自出版这种方式。

    thewhitetulip查看英文原文

    I've published a book on Go and one on Python on Leanpub with the "pay whatever you want model" I got much more money + satisfaction via this and organic traffic + reddit posting than what a top publisher was going to give me for a book They were going to give me 40k INR as upfront deposit and then some % on 1000 copies sold Contrast that with Leanpub, 1000s have downloaded my Go book, most of them have for free, while some have paid. Win-win. It is a big deal for me that 1000s have downloaded my book! Have received good feedback on email too from few. So overall, I love self publishing for technical publishing!

    同类还值得读

    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

    关注向阳乔木

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

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

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