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

    出版与作家生涯2015blogs.perl.org

    亚马逊上的虚假技术书评正在伤害我的书

    Fake Amazon Tech Book Reviews Are Hurting My Book

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

    导读

    一位 Perl 作者发现自己的书被大量虚假的亚马逊一星差评攻击,而且这些假评论都在推销同一本竞品书。几位评论者分享了类似经历,并给出识别假评论的实用方法。对写作者来说,这篇提醒我们:书评数量不等于作品质量,而读者写反馈时是否具体,才是可信度的关键。

    关键词 书评造假亚马逊评论评论可信度读者反馈

    可以直接用的写作要点

    1. 01

      别把评论数量和星级当成作品质量的证据——评论少于几百条时,亚马逊上的评分很容易被完全操纵。

    2. 02

      写书评或给别人反馈时,务必提到书中具体内容(章节、例子、观点),空洞的褒贬是最明显的造假信号。

    3. 03

      检验一条评论真假有个简单办法:如果一字不改也能套用到同类任何一本书上,那它多半没读过这本书。

    4. 04

      真实的口碑来自真实的读者,作者应主动建立小范围的读者群,而不是依赖公开平台的评分。

    HN 评论精选

    冷门书的评分极易被操纵,假差评常用来给竞品导流。

    我几年前写过一本冷门技术书,说实话读者很少。好评几乎全是我认识的人写的。后来开始出现一星差评,每条都没有实际内容,完全不提书里任何具体的东西,明显没读过。但每条差评都会提到同一本“更好”的竞品书。太明显了:有人在踩我的书来推另一本。一开始我还在意,请亚马逊删掉,删了又来,反复几次后我就累了,不再管了。

    dougmccune查看英文原文

    Anything with less than a real critical mass of reviews (less than hundreds) is way too easy to entirely game on Amazon. I wrote a book quite a few years ago on a niche tech topic. To be entirely honest, very few people read it. The positive reviews of the book were almost all from people I knew personally. Then the 1-star reviews started coming in. Each 1-star review had no actual content in the review. It was clear that the writers of these BS reviews hadn't read the book at all, since they didn't mention anything specific whatsoever. However, each of the 1-star reviews DID manage to mention a competing book that was "better". And all the bad reviews mentioned the same exact competing book. It was ridiculously obvious that someone was bashing my book to push a competing book instead, without any actual substance. At first I cared, and asked Amazon to remove the reviews, which they did. Then more BS reviews came back, I had them removed, they came back again, and eventually I just got tired and stopped caring.

    发现分类或评论问题可以向平台反馈,但要说清具体条目。

    如果你有几分钟,可以通过亚马逊的 24 小时在线客服提交“目录反馈”:选择“更多订单问题”→“给亚马逊反馈”→“其他反馈主题”,在文本框里输入“Catalog feedback”,点“Chat”。我花了大约五分钟说明 Perl 分类前 100 名里有几本书被错误归类,他们很爽快地接受了。附上分类页面的直接链接会帮上大忙,最好具体指出是哪个排名位置的哪本书放错了分类。

    floatingatoll查看英文原文

    If you have a few minutes to report the issues with the Perl category to Amazon, they accept "catalog feedback" through their 24/7 live chat system. https://www.amazon.com/gp/help/customer/contact-us #1: Ignore this section, skip to #2. #2: From the dropdowns, select: "More order issues", "Give Amazon feedback", "Other feedback topic". In the text box, enter "Catalog feedback". #3: Click "Chat". It took me around five minutes to explain that several of the books in the top 100 were incorrectly listed in the Perl category, and they happily accepted the feedback. Including a direct link to the Perl category helps them tremendously: http://www.amazon.com/gp/bestsellers/books/6134005011 And I also included a link to the post above. Edit: Tell them specifically which books, in which top 100 position, are in the wrong category, so that they know which ones aren't Perl.

    用“能否套用到任何同类书”这一条测试就能筛出大部分假评论。

    我希望亚马逊在每条评论上方加一个“这看起来是假的”按钮,我每周都会点好几次。多数假评论很好认,简单测试法是:这条评论是不是一字不改也能用来评价这个类别里的任何另一本书?我常在独立作者的 Kindle 书下看到假评论。一本书的质量标志是:没有明显的五星假评,但有几个人写的真实评论,哪怕只有三四条。有些假评更难识别,比如一个存在多年的账号,我怀疑背后不止一个人(也许是公关公司)在逐条手写独特评论:全是极端的一星或五星,内容只来自技术参数或产品描述,看不出真正用过产品。我认为真正好的评论也会被假投票打压——我自认为写得最好的一条评论反而被踩得最多。

    FilterJoe查看英文原文

    I wish Amazon had a "This looks fake" button above each review. I would click it multiple times per week. Most fake reviews are easy to spot. The simple test: Could this review have been written about any other book in this category without changing a word? I see fake reviews all the time for Kindle books written by indie authors. A mark of quality in a book is when there appear to be no 5 star fake reviews, but several written by real people, even if there are only 3 or 4 reviews. Some fake reviews are harder to spot, though. For example, I suspect this account, which has been around for many years, is more than one person (perhaps a PR firm) hand writing unique reviews for each one: http://www.amazon.com/gp/pdp/profile/A130YN8T37O833 All reviews are either 1 star or 5 star. There is content specific information but all stuff you can get from tech specs or descriptions - no sense the person actually used the product except generic intro paragraphs. I think there is also fake voting on really good reviews. The review that I felt was the best review I ever wrote was downvoted more than any other review I've written. I don't really know if the downvoting was fake - maybe it wasn't helpful because I delved into too much technical detail: http://www.amazon.com/review/R14QK0B7HRE5L8 However, most of the glowingly favorable reviews for this book have unanimous thumbs up, and the first 3 are written by "A Customer" which I'm guessing means the account of the reviewer has been terminated.

    高星评论堆积未必代表质量,独立出版领域尤其明显。

    网站打不开,附上网页缓存版本。顺便说一句,不太相关:我在亚马逊上经常看到一些五星评论很多、读起来却很糟的书,在独立科幻作者的 Kindle 独家书里尤其常见。当然,“糟”只是我的看法。

    impostervt查看英文原文

    Web cache version, since the site is down for me: http://webcache.googleusercontent.com/search?q=cache:blogs.perl.org/users/ovid/2015/03/fake-amazon-book-reviews-are-hurting-my-book.html While not really related, I seem to run across a lot of books on Amazon that have a high number of 5 star reviews that, upon reading, are just bad. Seems to happen a lot with books by independent sci-fi authors with Kindle-only books... Of course, "bad" is just my opinion.

    同类还值得读

    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

    关注向阳乔木

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

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

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