CHAPTER 03
Important Notes On This Book (Disclaimer)
Read It
Most people read a disclaimer and skip it. But this one is doing real work. The compiler is telling you something uncomfortable: this book is not a transcript. Naval's ideas were spoken, tweeted, interviewed, and then edited, rearranged, and sometimes quoted secondhand. What you're reading is a curated version of his thinking, not a verbatim record. The word "faithful" is the trap here. Faithful doesn't mean word-for-word accurate. It means the editor tried to preserve the sharpness of the judgment while admitting that context has been lost. Some quotes can't be verified. Some passages have been reshaped for clarity. The disclaimer asks you to accept a trade: you get a coherent, readable book, but you give up the certainty of exact quotation. That's a fair deal only if you know what you're giving up.
Open full image ↗Draw It
There are three layers that prose tends to collapse into one: the original expression, the recorded version, and the edited text. Each layer loses something—tone, context, precision—and each layer gains something—readability, structure, accessibility. The diagram separates these layers so you can see the distance between what Naval actually said and what you're reading. The citation markers aren't decoration. They're a path back to the source for anyone who wants to check. The formatting conventions—pull quotes, tweetstorms, bolded questions—are signposts that tell you which layer you're in. Without this separation, you'd either trust everything or trust nothing. The map gives you a way to calibrate.
Rethink It
I see the same problem in technical writing. Someone summarizes an architecture decision in a blog post, but they leave out the constraints, the arguments, the failed alternatives. If I copy their conclusion without knowing how far it is from the original context, I'm building on sand. The disclaimer's lesson is simple: before I act on secondhand information, I need to know how many layers it has passed through. A direct quote from a design doc is different from a paraphrase in a conference talk. Both can be useful, but they carry different weights. The more layers, the more I need to verify.
Take It With You
When I need precision, I go to the primary source. When I need understanding, an edited version is fine—but only if I remember what it lost.