技术写作与文档2019tunetheweb.com编辑精选
为 Manning 写一本技术书
Writing a Technical Book for Manning
导读
一位作者详细记录了在 Manning 出版社写技术书的完整流程：从选题、评审到编辑协作。对写作者的价值在于，它展示了专业出版背后密集的审稿与团队协作，也让人重新思考“作者署名”与“团队成果”的关系，并可与自出版路径作对比。
可以直接用的写作要点
- 01
把书当成团队产品：封面署你的名，但质量靠编辑、评审和审稿人共同打磨，任何一环都不可替代。
- 02
重视多轮外部评审：出版社肯在评审上投入多少，往往直接决定书的技术准确度和可读性。
- 03
动笔前先查同类书：如果同一主题短期内扎堆出版，出版社可能因不愿重复而撤约，选题时机本身就是写作决策。
- 04
自出版意味着全流程自负：写作、编辑、营销都要自己掌控，换来的是对书每个细节的完全主导权。
HN 评论精选
出版是团队协作，编辑与评审的专业投入不可替代，值得为质量再合作。
我为 Manning 写过《Relevant Search》，过程很折磨人，但文中很多说法我都能证实。Manning 确实懂怎么做出好的技术书，也真心把书当作一种媒介来投入，尽管外界总在喊“颠覆图书”；社里的人都把这当成手艺来做。还有一点：封面署的是作者的名，但工作其实是编辑、出版社、评审等一群人的团队成果，没有哪一环可以替代。如果再写一本，我还会考虑他们——不是因为他们让事情变简单，而是他们真的在乎我想要的质量。我也很喜欢他们五年前那种 Web 1.0 风格、只做书的网站。
softwaredoug查看英文原文
I wrote a book for Manning (Relevant Search). It was a grueling process. I can confirm much that's in here. I will say that I generally felt Manning (a) really understood how to craft good tech books (b) was really dedicated to tech books as a medium, despite all the attempts to 'disrupt books' which I respected (c) was full of dedicated people that treated this as their craft The other point I'll make is the author's name goes on the cover, but the work is really a team effort between dedicated editors, the publisher, reviewers, and others. No part is replaceable. If I was to write another book, I'd definitely consider doing it with them. Not because they made it easy, but because they really were dedicated to the quality I wanted in my book I also loved their super old school, Web 1.0, "we just do books" website 5 years ago :)
评审流程的透明度会直接影响读者和作者对出版社的信任。
这篇干货很多。读完后我更愿意在 Manning 出书、也更愿意买他们的书了。我当过 Packt 的技术评审，之后就尽量避免买他们的书。作为 Manning 的读者，我觉得他们更好；看到整个流程和评审的密度，我觉得他们整体上很不错。
danpalmer查看英文原文
Great post, lots of detail. After reading this I would be more likely to want to publish with and buy from Manning. I’ve been a technical reviewer for Packt, and since doing so would avoid buying any of their books. As a customer of Mannings’, they seem better, and seeing the inside of the process and the amount of review that happens, I think they sound great all things considered.
自出版的核心优势是全流程掌控，可专注写作与营销。
如果想了解自出版这条路，可以看我写的文章：我如何在 200 小时内写出一本 WebAssembly 书。这是我的第二本自出版书，我很喜欢这种方式——能专注于写作和营销，书里每个方面都由我亲自打磨。
raboukhalil查看英文原文
If you want to hear about the alternative approach of self-publishing, check out my post about how I wrote a WebAssembly book in 200 hours: https://medium.com/@robaboukhalil/how-i-wrote-a-technical-book-in-under-200-hours-911d5e4f9e8c?source=friends_link&sk=13c5b15048cf1c8676d6e208181462b7 This is my second self-published book and I've loved this approach. It lets me focus on writing and marketing, and I get to craft every aspect of the book.
选题撞车会导致撤约，写作前要评估同类书的竞争与时机。
写书是件折磨人的事。我曾和朋友签下合同、拿到 5000 美元预付，甚至写完了四分之三。结果一个月内同一主题出了十二本书，出版社撤了合同，因为不想再做“又一本书”。这理由说得通。他们很好心，让我们保留预付和已写内容的版权，其中一些后来变成了博客文章。
jedberg查看英文原文
Book writing is a punishing endeavor. I started writing a book once. We got a contract, we got an advance ($5,000), we even wrote 3/4 of the book. Then in one month twelve(12!) books came out on the same topic. The publisher pulled our contract because they didn't want to be yet another book on the same topic. That seemed reasonable. They were kind enough to allow us to keep the advance and maintain the copyright on what we had written, some of which were turned into blog posts.
同类还值得读
编写更好文档的框架
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 条写作要点编辑精选