技术写作与文档2017news.ycombinator.com
Ask HN：哪些公司的工程团队博客写得最好？
Ask HN: Which companies have the best blogs written by their engineering team?
导读
这篇 HN 讨论盘点哪些公司的工程团队博客值得读，评论里提到了微软、Google、Slack、Uber、Netflix、Percona 等，并延伸到博客定位、深度写作以及质量与数量的取舍。对写作者来说，它提供了不少可借鉴的选题思路：如何服务读者、如何持续输出有价值的技术内容。
可以直接用的写作要点
- 01
先明确博客要给读者什么：是独特案例、开发过程，还是两者混合，再据此决定选题和写法。
- 02
垂直领域的深度长文能长期积累搜索价值和行业影响力，值得坚持写透一个问题。
- 03
质量比数量更重要，为了营销而写空洞凑数文章，反而会伤害真正读者的信任。
- 04
有个人风格和专业视角的栏目或作者，往往比公司博客的整体输出更容易被记住。
HN 评论精选
大公司博客整体参差，但个人化、专业深耕的栏目能建立读者信任，甚至转化为购买和长期订阅。
我很喜欢微软的很多博客。整体质量参差不齐，但里面有精品。尤其是 Raymond Chen 的博客，好到让我买了他的书，而书也确实没让我失望。我还订阅了 Edge Dev Blog、Mark Russinovich、Games for Windows 和 DirectX SDK。另有一些很久没更新，比如 Larry Osterman，或者已经停更，比如 Rico Mariani。
shdon查看英文原文
I actually really like many of the blogs at Microsoft. It's a bit of a mixed bag, but there's some gems in there. Raymond Chen's blog[1] in particular was good enough to get me to buy his book (which definitely did not disappoint). Other ones I subscribe to are the Microsoft Edge Dev Blog[2] , Mark Russinovich[3] and Games for Windows and the DirectX SDK[4] And there's a few that have unfortunately not been updated for a long time, such as Larry Osterman[5], or have come to an end, such as Rico Mariani[6] [1] https://blogs.msdn.microsoft.com/oldnewthing/ [2] https://blogs.windows.com/msedgedev/ [3] https://blogs.technet.microsoft.com/markrussinovich/ [4] https://blogs.msdn.microsoft.com/chuckw/ [5] https://blogs.msdn.microsoft.com/larryosterman/ [6] https://blogs.msdn.microsoft.com/ricom/
工程博客可以按内容定位分类，写作前先想清楚读者想获得的是案例、方法还是流程。
这取决于你想从博客中得到什么。有些博客主要写团队遇到的独特或很酷的挑战，比如 Google、Slack；有些更关注如何用软件解决工程挑战以及开发流程，比如 Uber、Twitter；还有些两者混合，比如 Dropbox、Netflix。
Guyag查看英文原文
Depends what you want to get out of them. I find some are mostly focused around some of the more unique/cool challenges they come across (Google[1][2], Slack[3]), and others are more about how they solve the engineering challenges they face through software and/or about their dev process (Uber[4], Twitter[5]). Some are mix of the two (Dropbox[6], Netflix[7]). [1] https://developers.googleblog.com/ [2] http://research.googleblog.com/ [3] https://slack.engineering [4] https://eng.uber.com/ [5] https://blog.twitter.com/engineering [6] https://tech.dropbox.com [7] http://techblog.netflix.com/
质量与数量之间存在真实张力，写作者要在营销效果和读者对空洞内容的厌恶之间做权衡。
大家怎么看博客营销中质量与数量的相对效果？我们最近开始发布自认为质量很高的内容，其中多数上过 HN 首页，如果这能算指标的话。一位很懂营销的朋友建议我们多写一些凑数文章。我们很纠结，因为作为内容消费者，我们强烈讨厌空洞的东西。很想听听不同策略优劣的实际例子。
foob查看英文原文
What are peoples' thoughts on the marketing effectiveness of quality relative to quantity in blogging? We have recently started publishing what we consider to be very high quality material (the majority of them have front-paged on HN if that's any indication). Most of these have been published on [1] so far but we're in the process of transitioning to a more official company blog [2]. A close friend who really knows his way around marketing has been advising us to write more fluff pieces. We're really torn over this because we strongly dislike vapid content as consumers. I would be really curious to hear any anecdotes on the relative merits of the different strategies. [1] - http://sangaline.com [2] - https://intoli.com/blog/
长期、垂直、深度的技术写作能形成搜索资产和行业影响力，关键在于持续把专业问题写透。
Percona 不是传统意义上的工程博客。它从 2006 年左右开始，十多年来持续发布关于数据库性能和 InnoDB 内部机制的高质量深度文章。如果你曾以运维或 DBA 身份排查 MySQL 的奇怪性能问题，很可能在搜索结果里碰到它。免责声明：我目前受雇于 Percona，但这不是我分享它的动机。
tristor查看英文原文
Not an "engineering blog" in the traditional sense. Percona has been posting deep-dive high-quality pieces about database performance and the inner workings of InnoDB since around 2006, so more than 10 years now. If you've ever had to troubleshoot a weird performance issue in MySQL as an Ops guy or DBA, you've probably ended up finding this in your Google results: https://www.percona.com/blog/ Disclaimer: I am currently employed by Percona, although that is not my motivation for sharing this.
同类还值得读
编写更好文档的框架
A Framework for Writing Better Documentation
这是 Divio 的文档写作框架，把技术文档按「读者的目标」分成四类：教程（学习导向）、操作指南（问题导向）、参考（信息导向）、解释（理解导向）。
技术写作与文档2021 · 637 分 · 76 评4 条写作要点编辑精选写好一份设计文档
Writing a good design document
这篇 HN 帖子标题为《Writing a good design document》，主题是如何写好一份设计文档；对写作者来说，它值得作为技术写作和结构化说明文的参照。
技术写作与文档2025 · 581 分 · 147 评3 条写作要点编辑精选技术写作课程
Technical Writing Courses
这是 Google 官方免费技术写作课程（两门），讲受众定义、主动语态、短句、文档结构等基础方法。
技术写作与文档2020 · 571 分 · 73 评4 条写作要点编辑精选写出更好的错误信息
Write better error messages
这篇帖子讨论如何写出更好的错误信息，评论补充了开发者场景下的具体做法和真实反面案例。
技术写作与文档2022 · 566 分 · 253 评4 条写作要点编辑精选写一本技术书的经济账
The Economics of Writing a Technical Book
一位技术书作者拆解写书的真实经济账：版税收入往往远低于投入的时间成本。
技术写作与文档2018 · 519 分 · 149 评4 条写作要点编辑精选