Daily Productivity Sharing

Daily Productivity Sharing

Share this post

Daily Productivity Sharing
Daily Productivity Sharing
Daily Productive Sharing 243 - How to Write An O'Reilly Book

Daily Productive Sharing 243 - How to Write An O'Reilly Book

Dr Selfie
Jul 21, 2021
∙ Paid

Share this post

Daily Productivity Sharing
Daily Productivity Sharing
Daily Productive Sharing 243 - How to Write An O'Reilly Book
Share

One helpful tip per day:)

(The English version follows)

#note_taking

Justin Garrison 在几年前通过 O'Reilly 出版了一本技术书籍 Cloud Native Infrastructure,他介绍了不少出版前后的趣事:

  1. O'Reilly 的作者无权选择动物书封面上的图案,这些动物图案都由 O'Reily 安排;

  2. O‘Reilly 提供了一套线上写作系统,可以直接调用 git ,大大简化了技术写作的协同流程,但是后期的校对等环节并不试用这一系统,而是传统的电邮;

  3. 作者通过这本书获得了超过一万美金的收入,其中最大的部分来自技术公司的赞助;

  4. 整本书修改了非常多次,累计修改的细节超过2000处;

  5. 作者试用 git 来管理草稿,自己校对时会把纯文本的文档编译成 PDF 阅读。

以上这些经验其实也适用于博士论文写作,当然也可以参考我们之前分享的另外两本技术书籍的出版经历:

Designing Data-Intensive Applications - Daily Productive Sharing 228 - 20210630

An Elegant Puzzle and Staff Engineer - Daily Productive Sharing 223 - 20210623

如果你觉得今天分享有帮助,不妨把它分享给你的朋友

原链

The Economics of Writing a Technical Book

需要更棒的简历,不妨试试我们的 CV Consultation

如果你也想成为更高效的人,欢迎加入我们的 TG group


Justin Garrison, who published a technical book Cloud Native Infrastructure through O'Reilly a few years ago, describes a number of interesting facts before and after the publication.

  1. O'Reilly authors did not have the right to choose the animal artwork on the book covers, which were arranged only by O'Reilly;

  2. O'Reilly provided an online writing system that allowed direct link to git, greatly simplifying the collaborative process of technical writing, but post-proofreading and other aspects did not use this system, but traditional emails;

  3. the authors earned over $10,000 from the book, the largest portion of which came from sponsorship by technology companies;

  4. the book was revised very many times, with over 2,000 cumulative changes in detail;

  5. the author tried git to manage drafts, and compiled plain text documents into PDFs for reading when he proofread them himself.

Some of these are also applicable to PhD dissertation writing, and of course to the publication of two other technical books we have shared before.

Designing Data-Intensive Applications - Daily Productive Sharing 228 - 20210630

An Elegant Puzzle and Staff Engineer - Daily Productive Sharing 223 - 20210623

If you find today's sharing helpful, why not share it with your friends?

Link

The Economics of Writing a Technical Book

Need a superb CV, please try our CV Consultation

This post is for paid subscribers

Already a paid subscriber? Sign in
© 2025 Dr Selfie
Privacy ∙ Terms ∙ Collection notice
Start writingGet the app
Substack is the home for great culture

Share