Building Judgement
A chapter summary from The Almanack of Naval Ravikant by Eric Jorgenson.
Once the wealth-building framework is in place, the binding constraint becomes judgment: making the right decisions inside the framework. Naval argues that judgment cannot be taught directly but is built through specific reading, specific practice, and specific exposure to consequences.
His reading prescription is unusual. Read the foundational texts in domains you care about — original works by serious thinkers rather than derivative summaries. Read across multiple unrelated domains so that you build the mental hooks to recognize patterns. Read slowly, re-reading the parts that resist understanding rather than skimming through them. The quantity-of-reading metric most people optimize against is wrong; the depth of engagement is what produces durable judgment.
The practice component is making decisions in the real world with consequences you bear. Reading alone produces vocabulary; making decisions and observing the results is what calibrates the vocabulary into judgment. Naval's argument is that the best way to develop judgment in any domain is to take small bets, observe the outcomes, and update your model of the domain based on what actually happened rather than what you expected.
The exposure component is curating your information diet for signal rather than entertainment. Twitter, news, opinion media — these produce constant input but very little signal. Books, papers, the slow exchange of correspondence with serious people — these produce less input but higher signal per minute spent. The judgment-building project requires defending against the high-volume low-signal default that the modern information environment otherwise installs.
A short summary — and that's the point. Read Stacks chapters are deliberately tight. The full The Almanack of Naval Ravikant edition has the examples, the longer argument, and the moments worth re-reading. If this resonated, the Amazon link below buys the actual book and supports the author.
One chapter a week — curated, not algorithm-picked.
If this resonated, the free weekly Read Stacks email sends one curated 4-book stack with the chapter we'd open first. No spam, unsubscribe anytime.
More from The Almanack of Naval Ravikant
From Read Stacks · Learn
If you just read a chapter summary…
You're using the navigation tool the way it was designed to be used. Two short essays on the meta-skill — what summaries actually preserve, and the six retention techniques that decide whether what you just read is still useful six months from now.
- Are book summaries actually useful, or am I just cheating?
Chapter summaries are a navigation tool, not a substitute. Used right, they help you read more books fully — by helping you avoid the wrong ones. Used wrong, they're a comfort blanket that lets you feel like you're reading without engaging with the material.
6 min read
- I read a lot of books but can't remember anything. What works?
Forgetting most of what you read is normal, not a personal failing — your brain wasn't designed to retain prose at the rate modern readers consume it. The practices that DO work share one thing: they force you to USE the material instead of just consuming it. Six specific techniques, each tested across decades.
7 min read