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

    出版与作家生涯2020theguardian.com

    安娜·维纳谈她的书《荒芜之地》

    Anna Wiener on her book “Uncanny Valley”

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

    导读

    这是《卫报》对安娜·维纳的访谈,谈她的回忆录《Uncanny Valley》。这本书讲她如何在硅谷初创公司工作四年,观察科技行业里的监控、权力和道德空缺。对写作者来说,值得看的是她如何把亲历的行业经验写成有距离感、有批判性的叙事,以及从杂志长文到出书的路径。

    关键词 非虚构写作硅谷文化回忆录标题写作

    可以直接用的写作要点

    1. 01

      把一段亲身经历当成田野调查来写:先积累素材和观察,再动笔成书。

    2. 02

      写行业题材时,用具体场景和细节呈现文化,而不是直接下判断。

    3. 03

      先写杂志长文试水,再扩展成书,是可行的非虚构写作路径。

    4. 04

      标题和开头要让不了解内情的读者也能看懂,别只靠圈内人名和书名吸引人。

    HN 评论精选

    长文先发杂志、再扩展成书,是一条可借鉴的写作路径。

    这篇后来成书的文章最早发表在文学杂志 n+1 上,链接是……(顺带调侃:在文学杂志名里,'n+1' 算是挺好理解的哈哈)

    russler23查看英文原文

    Essay from n+1 that led to the book: https://nplusonemag.com/issue-25/on-the-fringe/uncanny-valley/ (As literary magazine names go, “n+1” is pretty relatable haha)

    长期行业观察加上道德视角,能让科技写作不止于猎奇。

    她听起来像职业作家,我怀疑那四年其实是在为计划中的书做调研;这种事很常见,而且显然奏效了——书还没出,她就已经是热点,还当上了电影执行制片人,这很“硅谷”。我自己的视角有点特殊:我从 1983 年用机器码开始编程,在一家顶级日本企业待了大半职业生涯,那是个“孤岛”,和硅谷文化几乎没有可比性。离开后我发现,钱既腐蚀人又给人能量:它推动增长、创新和活力,也带来近乎彻底的道德真空。那家日本公司有很多毛病,但团队精神和极高的伦理标准让我印象深刻。

    ChrisMarshallNY查看英文原文

    It's interesting. She sounds like a pro writer. I wonder if her four years were really research for a planned book. That kind of thing is very common. If so, it's paid off. She's hot news, right now. Being exec producer on a movie before the book is even out, is sort of...Silicon Valley. My own perspective is kinda weird, and I don't pretend to be an expert in the culture. I started programming in 1983, with machine code, and I've been doing this stuff a very long time. As I look around at folks in the industry, I see that it is a very long time, indeed. There's not many people with the length of time in the industry I have (which is not necessarily something that has been beneficial to me). I spent most of my career at a top-shelf Japanese corporation. It was a frustrating, but also awesome, experience that has almost no analogue at all with Silicon Valley culture. It was basically a "silo." After leaving that company a couple of years ago, I have been acclimating to a vastly changed landscape. It's been rather eye-opening. The one thing that has struck me the most, is that money seems to have become rather corrosive, while also energizing. It powers a lot of growth, innovation and energy, but also brings with it an almost complete moral vacuum. The Japanese corporation had many flaws, but I was impressed by their focus on teamwork and almost insanely high ethical standards (It was a very "old-fashioned" company). I regularly worked (and argued) with some of the most brilliant scientists and engineers in the world. I like the energy, and I think some of the tools and techniques that have developed are really nice, but I have been rather taken aback by the manner in which our culture is expressed, these days. It's very different from the rather "scrappy" and hopeful way we thought about things back when. I'm figuring out how to navigate the new world. I need to learn how to work in the fast-paced, cutthroat culture, while holding to my ethical compass, and my workflow.

    标题要让陌生读者也能看懂,不能只靠人名和书名。

    不管是谁改了标题,都应该改回能准确反映内容的版本——原来那个就很好。不了解安娜·维纳或《Uncanny Valley》的人,根本看不懂现在这个标题。

    irq11查看英文原文

    Whomever changed the headline should change it to something that accurately reflects the content, like it was before. Nobody who doesn’t already know Anna Weiner or Uncanny Valley would understand the meaning of the headline.

    用一句话说清人物、书名和核心议题,是让读者进入陌生题材的有效写法。

    补充点背景,因为标题确实需要改进:安娜·维纳曾是 GitHub 员工,她写的《Uncanny Valley》讲硅谷的“不受监管的监控、冷酷的老板、性骚扰”等。另据原文:2018 年 1 月环球影业买下电影改编权,剧本还在初期开发阶段,维纳担任执行制片人。

    jagged-chisel查看英文原文

    Bit of context since the title needs improvement: Anna Wiener, a former GitHub employee, authors a book titled "Uncanny Valley" about "Unregulated surveillance, ruthless bosses, sexual harassment..." in Silicon Valley. Also, from TFA: "in January 2018, Universal Pictures optioned film rights; the screenplay is now in its initial development stages and Wiener is executive producer."

    同类还值得读

    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

    关注向阳乔木

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

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

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