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

    博客与个人写作2019news.ycombinator.com

    Ask HN:最好的博客平台是什么?

    Ask HN: Best Blogging Platform

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

    导读

    这是一则 Hacker News 的问答帖:一位想开博客的人希望「专心写作、不折腾服务器维护」,同时又要一定的自定义能力和独立域名,社区围绕静态站点生成器与 WordPress 给出了不同路线的建议。对写作者来说,值得读的不是技术选型本身,而是这场讨论暴露出的常见陷阱:为了「完美工具」而无限拖延,最后写出来的字反而最少。

    关键词 博客平台写作工具静态站点少折腾

    可以直接用的写作要点

    1. 01

      选博客平台的唯一标准是「它让你多久能发出第一篇文章」,而不是功能清单有多长。

    2. 02

      警惕「工具拖延症」:周末都在调配置、改主题、学部署,最后只收获一个漂亮的空博客。

    3. 03

      先问自己是否真的需要插件和深度自定义;多数个人博客只需要一个能写字、能发布的文本框。

    4. 04

      如果自己不擅长技术,就用托管服务或让别人代管技术部分,把注意力留给写作本身。

    HN 评论精选

    静态站点生成器容易变成折腾工具的无底洞,反而挤掉了写作时间。

    如果你只是列了那些需求,那选 WordPress 就够了。更新并不难,核心更新可以设成自动,它会把该做的都做了。但如果你在一个周末折腾完代码后想「我还要再写更多代码」,那你会选静态站点生成器——然后这个周末做不完,下个周末还得继续弄;最后你用一个「勉强够用但不太满意」的版本上线,放了几周不管;再回来时已经忘了怎么发布、怎么构建、怎么部署,只能翻 shell 历史记录找命令。哪天想补上当初没做的功能,又得把学过的全部重学一遍。有人有过这种经历吗?我说的是 Hugo,但其他工具大概也一样。WordPress 在自定义和易用之间的平衡足够好,能让你直接开始干活。

    gexla查看英文原文

    If you have a gun pointed to your head with the requirements you have listed then you go Wordpress. Updates aren't difficult. I'm not sure about plugins (I haven't used WP in a long time,) but you can set the core Wordpress updates to be automatic. It will handle everything you need. If after a week of coding you arrive to the weekend and think "I want to do a bunch more coding" then you go with a static site generator. Then you don't finish over the weekend and have to screw with it the following weekend as well. Then you finally publish the thing with "good enough but not quite what you wanted" functionality and let it sit there for weeks. Then you come back to it and scratch your head trying to remember how to publish / build / deploy it (or you cycle through your shell history hoping the commands are still in there.) One day you decide that you want to add that functionality you left out the first time and find that you have to relearn everything you had to learn to build the thing in the first place. Sure, you vaguely remember the easy stuff, but you have to refresh on the easy stuff to get back to the harder stuff which you never had time to figure out from the beginning. Anyone been there? ;) In this case, I'm thinking of Hugo, but I imagine it's much the same for all the others. With Wordpress you get enough balance of customization and ease of use that you can just get on with it. If you need a bit of help, then get on Fiverr or similar and have someone throw you pointers (or just do it for you) to save you time in getting past tricky parts. There's a reason loads of sites on the internet are using WP. People use it to GTD and move on to something else.

    托管型 WordPress 把维护外包出去,兼顾自定义与「只管写」。

    虽然 WordPress 在 Hacker News 上似乎不太受欢迎,但我认为它是博客的绝佳平台:社区很棒、文档极其丰富,而且完全可定制。如果走托管方案,多数公司会替你处理安全和更新,你可以专心写作,把技术活交给别人。我就在做这样一个托管服务,目前在内测;印象中做得比较到位的公司有 Kinsta、Pantheon 和 Presslabs。

    jamesponddotco查看英文原文

    While it doesn't seem very popular in Hacker News, I think WordPress [1] is an excellent platform for a blog. The community is terrific, there is a tremendous amount of documentation out there, and it is entirely customisable. If you go with the managed hosting route, most companies handle security and updates for you, so you can focus on writing and leave everything technical to someone else. I am working on one myself — and have a private beta running, if you are interested [2], —, but of the top of my head, some companies that will go above and beyond as far as WordPress is concerned, include Kinsta [3], Pantheon [4] and Presslabs [5]. The last one is based in Romania and open sourced a bunch of their stack, worth checking out. [1] https://wordpress.org [2] Just email me at help@madpony.co for information [3] https://kinsta.com [4] https://pantheon.io [5] https://www.presslabs.com

    极简的生成器(全部逻辑只有一个文件)让定制成本低到几乎等于写脚本。

    如果你喜欢写 Python,我推荐 makesite.py(GitHub 上的一个项目):正如它的 README 所说,这是一个简单、轻量、没有黑魔法的静态博客生成器,全部代码都在一个文件里。把内容放进 content 目录,运行 python3 makesite.py,它就会把生成的博客写进 _site 目录;再把这个目录复制到你想要部署的地方(比如启用 GitHub Pages 的仓库、VPS、云存储等)。它开箱即用,也高度可定制,因为要改的话,只需修改或自己编写 Python 代码。声明:这个项目是我妻子写的,我自己用它来生成我的静态博客。

    susam查看英文原文

    If you like writing Python code, I recommend https://github.com/sunainapai/makesite (makesite.py). As the README says, it is a simple, lightweight, and magic-free static blog generator. The entire static blog generator code is in a single file named makesite.py. Add your content to the `content` directory. Then run `python3 makesite.py` to generate the static blog. It writes the generated blog to the `_site` directory. Finally copy this directory to wherever you want to serve your blog from, e.g., GitHub repo with GitHub pages enabled, virtual private server, cloud storage, etc. It works pretty well out of the box and it is highly customizable too because doing so involves just modifying the existing Python code or writing your own Python code. Disclaimer: This project has been written by my wife. I use it myself to render my static blog at https://susam.in/.

    按自己熟悉的语言选生成器,再用托管服务把运维成本降到最低。

    想避开更新和病毒,就用静态站点。优秀的静态站点生成器很多:我的博客用 Jekyll,Hugo 也很流行,我试过 Gatsby,评价不错;Eleventy 最像「JavaScript 版的 Jekyll」。既然你想自定义,建议根据生成器所用的语言来选:喜欢 Ruby 用 Jekyll,喜欢 Go 用 Hugo,喜欢 JavaScript 用 Gatsby 或 Eleventy,其他语言就搜「[语言] static site generator」,看看 GitHub 星数有多少。选好之后,多数托管商都支持自定义域名,Netlify 免费且好用,我现在就用它;以前我放在 DigitalOcean 上,但 Netlify 更省心,尤其是打补丁和运维方面,而且自带 CDN,你的站点会更快。

    dceddia查看英文原文

    To avoid updates and viruses, go with a static site. There are a ton of good static site generators out there. My blog[0] runs on Jekyll[1]. Hugo[2] is a popular option. I've fiddled with Gatsby[3] and heard good things. Eleventy[4] looks as close to Jekyll-but-in-JavaScript as I've seen. Since you want to be able to customize it, I'd probably take the static site generator's language into account. Do you like... Ruby? -> Jekyll[1] Go? -> Hugo[2] JavaScript? -> Gatsby[3] or Eleventy[4] Some other language? -> google "[language] static site generator" and see how many GitHub stars it has. Once you've figured that out, most of the hosts support custom domains. Netlify[5] is free, and works very well. It's what I use currently. I used to host my site on DigitalOcean[6], but Netlify is definitely more painless, especially from a devops/patching standpoint. Plus it has a CDN so your site would be faster. [0] https://daveceddia.com/ [1] https://jekyllrb.com/ [2] https://gohugo.io/ [3] https://www.gatsbyjs.org/ [4] https://www.11ty.io/ [5] https://www.netlify.com/ [6] https://www.digitalocean.com/

    同类还值得读

    1. 我坚持每天写一条 TIL,已经写了一年

      Show HN: I've been writing daily TILs for a year

      这篇展示作者一年每天写 TIL(Today I Learned)并整理到 GitHub 仓库的做法。

      博客与个人写作2016 · 819 分 · 150 评4 条写作要点编辑精选
    2. 如何写出开发者愿意读的博客文章

      How to write blog posts that developers read

      这篇(正文与评论未提供,仅从标题判断)讨论面向开发者写技术博客的方法:怎样让忙碌的工程读者愿意点开、读下去并读到结尾。

      博客与个人写作2025 · 603 分 · 154 评4 条写作要点编辑精选
    3. 博客写作风格指南

      A blogging style guide

      这是程序员兼博主 Robert Heaton 的博客写作风格指南,用几十条简短规则讲如何让技术文章更清晰、更好读。

      博客与个人写作2018 · 495 分 · 188 评4 条写作要点编辑精选
    4. 十年职业博客写作,我学到了什么

      Ten years of professional blogging – what I’ve learned

      这是作者回顾十年专业博客写作经验的总结,评论补充了写作作为深度学习、聚焦主题、保护写作习惯和选择发布平台等实践。

      博客与个人写作2017 · 362 分 · 126 评4 条写作要点编辑精选
    5. 十年博客写作教给我的事

      What I learned in ten years of blogging

      这是一篇博客作者十年写作经验总结,核心观点是写作的价值在于持续积累而非单篇爆款。

      博客与个人写作2018 · 356 分 · 162 评4 条写作要点编辑精选

    打赏支持

    打赏二维码

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

    WeChat

    关注向阳乔木

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

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

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