I wrote previously about some of the statistics about The DevOps Handbook:
- 5+ years in the making
- 23 chapters
- 48 case studies
- 101,365 words (134,000 with the index)
- 48 images
- 509 endnotes
- 192 footnotes
Personally, I have a tremendous sense of satisfaction about the 509 endnotes. In some ways, the citations (in the form of endnotes) show the foundations that the book is built upon, both in the principles, practices, metrics and case studies.
Because of the nature of this book, unlike almost all of my previous projects, we felt it was important that every statistic and quote was cited—as well as thoroughly fact-checked. We wanted every citation to be easily found.
(Achieving this last objective required quite a bit of work. Many of the citations in the earlier versions of the manuscript pointed to hour-long videos, so a team of people worked to verify that the quote was accurate, often corresponding with the speaker to ensure that the spirit and intent of their quote was preserved.)
To make this as easy as possible for readers, I’ve posted all the endnotes to a GitHub repository, as well as BibTex bibliography file that we used for citations for early drafts that were in LaTeX. (The long story of how the manuscript started there in a GitHub repository, moving later to Google Docs, and then to Adobe InDesign, and now finally back to AsciiDoc in GitHub deserves its own blog.)
Here are the endnotes posted in their own GitHub repo.
Each endnote is provided as follows: a page number (from the paperback), three words from the sentence that the word is anchored to, and then the citation. (The citation style of putting the three words form the sentence is very cool, but was new to me… This apparently is called “endnotes keyed to text,” as described here.)
Lastly, here’s a word cloud of the citations, with “ibid” replaced by the full citation. (Ibid is from ibidem, meaning “in the same place.”) The book was edited according to Chicago Manual of Style, which explains that ibid “usually refers to a single work cited in the note immediately preceding. … It takes the place of the name(s) of the author(s) or editor(s), the title of the work, and as much of the succeeding material as is identical.”
You can clearly see who and what influenced The DevOps Handbook.
I hope this is helpful, and let me know what you think!