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

    写作方法2012coderwall.com

    小贴士:为自己而写

    Protip: Write for you

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

    导读

    这是 Hacker News 上关于"为自己写作"这一建议的讨论。发帖者主张写作首先应为自己而写,而评论者补充了重要平衡:为自己写能保持动力,但要真正进步,还需要编辑、读者和持续练笔的约束。对写作者来说,这组讨论点出了"自我表达"与"外部反馈"之间该怎么取舍。

    关键词 为自己写作编辑反馈写作习惯流量焦虑

    可以直接用的写作要点

    1. 01

      为自己写作能降低心理门槛、保持长期动力,但别把它当成拒绝修改和反馈的借口。

    2. 02

      找到一位你信任的编辑,让对方毫不留情地删改你的文字,进步速度会远超独自摸索。

    3. 03

      别把博客流量数据当作写作的首要目标,把注意力放回"写自己愿意重读的内容"。

    4. 04

      把写作变成随手可做的习惯:随身带笔记本,先写意识流草稿,允许早期作品是垃圾。

    5. 05

      认真对待废弃率:大量草稿被扔掉是正常的,关键是不把半成品直接公开发布。

    HN 评论精选

    为自己写的同时也要对读者负责,别把半成品直接发布。

    我对"为自己写还是为读者写"这件事很矛盾。今年初开始写博客,至今只发出四篇还看得过去的文章,远没达到每月一篇的目标。最让我意外的是自己写得多差:八成以上的内容都被我扔掉了。写代码要是这样我早失业了,但我没法让半成品草稿进入永久公开记录。很多人缺少这种克制,所以网上才有大量糟糕的文字,像 Joel Spolsky、Steve Yegge 那样的作者少之又少。所以,为自己写可以,但也请为读者写,对大家都好。

    brianwillis查看英文原文

    I'm really of two minds about the write for you/write for an audience argument. I started blogging early this year, and so far I've written and published four posts that don't make me want to gouge my eyes out. That's not to say that what I've written is especially good, just that it's passable. When I started I was shooting for one post a month, so I'm obviously way behind on what I thought was a conservative goal. What surprises me most about the whole exercise is how overwhelmingly bad I am at writing. More than 80% of the content I've written has been thrown away. If I wrote code like this I'd have been out of work long ago, but I just can't bring myself to go on permanent record with half-baked poorly thought out blog posts. I hate to put this so bluntly, but many people out there lack this kind of restraint. As a consequence, there's just a universe of truly awful writing online. The Joel Spolskys and Steve Yegges are really few and far between. So yeah, write for you, but if you don't mind, could you do the world a service and write for the rest of us too? We'll all be better for it.

    为一位信任的编辑而写,是比为自己写更快的成长路径。

    几年前我一时兴起创办了一本杂志,因为没钱请一流作者,只能和一批有热情但技巧不成熟的作者反复打磨稿件。这段经历让我明白:"为自己写"在一定程度内很好,但真想成为好作者,你需要为一位编辑而写——找信任的人把你的文字改得面目全非。为自己写太容易找借口:"读者没来是因为 x",而 x 永远不是"我写得差"。为好编辑写作会让你进步得快到难以想象。如果你能写代码,你离好作者已经走了 95% 的路。

    hluska查看英文原文

    A few years ago, I thought to myself, "Self, you haven't started a really stupid business with a remarkably high chance of failure in a long time. Why don't you start a magazine?" I was bored, so I did. Within a few months, I had founded a magazine. My co-founder and I bootstrapped it, so we didn't have access to the highest caliber of writers. Consequently, we did a whole lot of development work; taking writers with passion and some technical flaws and working with them until they could bang out some good quality content. I learned something really valuable working with young writers. The 'write for you' advice is great...to a point. If you really want to become a good writer, you need to write for an editor. Find someone you trust and get him/her to butcher your writing. Write for that person. The problem with writing for yourself is that it is too easy to say, "well, the audience didn't come because x." (where x != my writing sucks) The joy of writing for a good editor is that you will improve faster than you can possibly imagine. And then, you can say, "who cares about an audience, I'm a better writer now." You can become a great writer...anyone can. Hell, if you can write code, you're already 95% of the way there. My email address is on my profile - if you want someone to edit your stuff, send me some mail...

    别被流量数据绑架,把时间还给写作本身。

    建议:别统计你博客的访问数据。这说法有点争议,但这是我第一次真正在意自己做的博客,原因正是我不再关心统计。以前我最看重流量,沉迷于查看访问量涨了多少,花了太多时间看数据;而那些时间本该用来写我自己愿意重读的内容。

    Alan01252查看英文原文

    Protip: Don't track statistics on your blog. Little controversial, but this is the first time in my life I actively care for a blog I've created. And the reason? I don't care about the statistics. Previously my main priority was getting traffic. I became obsessed with looking at statistics to see how much traffic I'd gained. I spent far far too much time looking at statistics, when instead, I should have been doing, what I hope I'm doing now. Writing content that I will want to read again.

    随身记录、降低动笔门槛,先写起来,允许早期作品是垃圾。

    我写个人博客是因为有个想法必须从脑子里倒出来,不写下来它就会一直发酵、干扰我做别的事。我也随身带纸笔,记下的东西有时变成博文,有时变成故事;现在手边笔记本里有六个游戏点子、四个商业点子和几十篇雏形随笔,博客里的草稿也几乎是已发布文章的两倍。两年前我不是这样,那时给我纸笔能空几个月。改变的方法是把记录想法变得毫不费力:随身带本子,起步时先写意识流笔记。结论就是先开始写——早期的东西现在看都是垃圾,但它们帮我养成了写的习惯。

    JamesLeonis查看英文原文

    I write a personal blog because I want to get an idea out of my head. It's almost a pathological need to put it to paper or bits, or else it festers inside and distracts me from what I want to do. This post here is here because of that need. Other ways I deal with this need is carrying physical notebooks and a pen just about everywhere I go. Sometimes I turn them into blog posts. Sometimes I turn them into stories. Right now there are about six game ideas and four business ideas in the notebook next to me, as well as dozens of proto-essays. My blog likewise has almost twice as many "draft" essays than published posts. This wasn't the norm for me two years ago. If you were to give me a page and a pen then, it would be blank for months. I made a decision to make it easy and effortless to write down ideas and thoughts. That meant carrying around a notebook and pen to many places I went. I also started doing stream-of-thought notes to try and jog my noggin when I was first starting out. The takeaway here is to just get started. All my early stuff is garbage now, but it served as a good first wave to get me in the habit of writing.

    同类还值得读

    1. 被低估的工程技能:把文章写好

      Undervalued Engineering Skills: Writing Well

      这篇文章讨论为什么“写得好”是被低估的工程能力,以及它如何在团队协作、系统设计和职业发展中持续带来回报。

      写作方法2019 · 1,109 分 · 371 评4 条写作要点编辑精选
    2. 每行只写一句话:让写作和修改都更轻松的排版法

      Writing one sentence per line

      这是 Derek Sivers 的一篇短文,主张写作时每行只放一个句子,而不是按段落排版。

      写作方法2022 · 849 分 · 297 评4 条写作要点编辑精选
    3. 书面沟通是远程工作的超级能力

      Written communication is remote work super power

      这篇文章讨论远程工作中书面沟通的价值,评论区则补充了异步与同步沟通的适用场景,并提醒读者:备忘录、结论先行、结构化命令格式等书面沟通传统早已有之。

      写作方法2020 · 831 分 · 190 评4 条写作要点编辑精选
    4. 如何写出有用的文字

      How to Write Usefully

      保罗·格雷厄姆在这篇文章里给"有用的写作"下了一个可操作的公式:有用≈重要×新颖×正确×清楚,任一项为零,整篇文章就等于零;他还主张敢下确定判断、删掉让自己心虚的句子。

      写作方法2020 · 821 分 · 285 评4 条写作要点编辑精选
    5. 如何写得更清楚、想得更清楚,并学会复杂材料(PDF)

      How to write more clearly, think more clearly, and learn complex material [pdf]

      这份 PDF 讨论如何把文章写清楚、把思路理清楚,并用写作来学习复杂材料。

      写作方法2022 · 779 分 · 153 评4 条写作要点编辑精选

    打赏支持

    打赏二维码

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

    WeChat

    关注向阳乔木

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

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

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