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

    出版与作家生涯2010mixergy.com

    采访丹尼尔·布鲁西洛夫斯基:被 TechCrunch 解雇的作家

    Interview with Daniel Brusilovsky, The Writer That TechCrunch Terminated

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

    导读

    这是 Mixergy 对少年写手 Daniel Brusilovsky 的访谈——他因在 TechCrunch 任职期间向报道对象索要 MacBook Air 而被解雇。对写作者的价值在于:它揭示了科技媒体的编辑流程、未经审核发稿的风险,以及年轻写手如何在职业伦理上踩坑。

    关键词 科技媒体编辑流程职业伦理访谈写作

    可以直接用的写作要点

    1. 01

      发稿前必须经过编辑审核,尤其是涉及利益冲突的报道——'先斩后奏'在正规媒体是不可接受的。

    2. 02

      写手要清楚自己的职业边界:向报道对象索取任何好处,即使没拿到、即使只是玩笑,也会毁掉自己的信誉。

    3. 03

      入职时明确自己的身份、职责和流程(有没有合同、谁审核稿件),能避免日后说不清的责任纠纷。

    4. 04

      访谈式写作可以不追求对抗性:像 Andrew 那样'帮人建立而非拆毁'的提问方式,也能挖出好故事。

    HN 评论精选

    对比正规媒体的编辑审核制度,指出 Daniel 未经批准发稿和流程缺失是问题的关键。

    值得注意的几个细节:1) Daniel 承认他未经 TechCrunch 编辑批准就发布了第一篇报道。我在 The Escapist 写了近三年稿,16 岁开始,写作和研究完全自由,但发布必须经编辑审核,编辑甚至希望我在周末发布前打电话知会一声。我们和 TechCrunch 的区别可能在于我们追求质量而非抢新闻。2) 他 2009 年 6 月以实习生身份加入时,TechCrunch 没让他签任何文件、也没给头衔。3) 他对 TechCrunch 的管理结构和编辑流程提供了很好的内部视角。4) 他承认自己没有任何技术背景。5) 涉事公司是 TechCrunch 此前多次报道过的。6) 他说从未收到那台 MacBook Air,公司要求的那种文章也从未写出来。7) 他说自己没有敲诈过公司,但从 Intel 收到过与另一个项目相关的产品。

    loganfrederick查看英文原文

    Moments worth pointing out: 1. Early in the interview Daniel admits that he even published his first story without approval from TechCrunch editors. I spent almost three years writing for The Escapist (http://escapistmagazine) and started when I was 16. When it came to writing and researching, I was given free reign. However, when it came to PUBLISHING, it was made pretty clear that an editor would have to vet the story before it was released. Editors would prefer that I call them on weekends and at least give them a heads up on the situation before releasing a story. We might've differed from TechCrunch in that we strove for quality as opposed to breaking news. Point being that the Escapist editorial system worked very well, with everyone knowing the content going onto the site. 2. TechCrunch didn't have Daniel sign any paperwork or give him a title when he joined as an intern in June 2009. 3. In general, Daniel does provide a really good insight into how TechCrunch operates: management structure, the editorial process, etc. 4. Admits he doesn't really have any technical background. 5. Says the company involved was one that TechCrunch had covered multiple times before. 6. Says he never received the Macbook Air and the type of post the company requested was never written. 7. Says he has not extorted companies for products, but received products from Intel for an unrelated project he was involved with that he discusses on his blog. 8. The evidence used against him were joking IMs and emails. 9. Received an iMac from a friend who works at a tech company as a thank you for making an introduction to another company, not for TechCrunch posts. Then later wrote about one of the companies that was involved in a big legal discussion with Apple (iPod Rip). 10. Advice Daniel received from Mike Arrington the night before Teens in Tech (Daniel's conference): Neither party wants to have a public fight about this. This was another quality Mixergy interview revealing Daniel's side of the story and more details about a still mysterious topic. The entire interview is worth viewing.

    核心观点:没拿到好处不能开脱——'开口索要'这个行为本身就已越界。

    Daniel 强调他从未真正收到那台 MacBook Air,似乎以为大家知道这一点后会转而同情他。但我觉得他没意识到:即使没拿到好处,一开始去索要这件事本身(不管是不是开玩笑)就已经不可原谅了。尽管如此,我不认为这件事会对他造成长期影响,生活还要继续,等下次有人指责 Mahalo 玩 SEO 花招时,这一切都会成为过去。我觉得更大的新闻是他能和 Woz 深夜聊 IM,真让人嫉妒!

    covercash查看英文原文

    Daniel stressed the fact that he never actually received the MacBook Air and he seems to be under the impression that opinions will sway in his favor once people realize this. I don't think he realizes that just because he never received the payout doesn't excuse him from asking for it in the first place (whether he was joking or not). Despite all of that, I don't think this kid is going to be too impacted by all of this in the long run. Life goes on. Someone will accuse Mahalo of more SEO trickery and all of this will be a thing of the past. I think the bigger story here is that he gets to have late night IM sessions with Woz. I'm jealous!

    赞赏访谈者选择建设性而非对抗性的提问姿态。

    Andrew 的这句话让我耳目一新:'我不想做一场对抗性的访谈,要么狠批他、要么抨击 TechCrunch。那不是我。我想帮人建立,而不是把人拆掉。'

    rgrieselhuber查看英文原文

    I find this refreshing about Andrew: "I didn't want to do a confrontational interview where I'd either come down hard on him or slam TechCrunch. That's not me. I want to help build people up, not tear them down."

    提醒:过早过成人化的职业生活,可能让年轻写手失去真诚与分寸感。

    只有我觉得这整件事有点让人沮丧吗?这孩子才 17 岁吧?他确实很出色,但已经过上了 24/7 的生活方式,连度假都带着笔记本?他听起来像 35 岁。我希望有一天他能多找回一点自我,否则他给人的印象只会是个讨厌鬼,而不是神童。

    yankeeracer73查看英文原文

    Am i the only one who found this whole thing kind of depressing? this kid is 17, right? he's very impressive, but talking already about how he lives a 24/7 lifestyle and brings a laptop with him on vacation? he sounds like he's about 35. i hope one day he gets in touch a little more with himself or he's just going to come across like an ass, not a wunderkind.

    同类还值得读

    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

    关注向阳乔木

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

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

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