technical books are not novels.
if you read them linearly, you waste time and retain nothing.
the goal is not completion.
the goal is internalizing usable structure.
1. don’t start at page one
page one is usually context, not substance.
first pass:
- read the table of contents
- scan chapter summaries
- identify the core spine of the book
you are building a map, not collecting sentences.
2. read with a question, not curiosity
curiosity is weak. questions focus the mind.
before each chapter, decide:
- what problem is this solving?
- what capability does this unlock?
- where would this be used?
if a section answers none of these, skim it.
3. treat equations as compressed meaning
equations are not decorations.
when you see one:
- identify every variable
- map each term to a physical or logical meaning
- ask what happens if a term goes to zero or infinity
if you can’t narrate the equation, you didn’t read it.
4. stop at every definition
definitions are load-bearing walls.
rules:
- never skip definitions
- rewrite them in your own words
- connect them to something you already know
misunderstood definitions poison everything downstream.
5. read actively, with friction
smooth reading means shallow understanding.
do this instead:
- pause often
- re-derive results on paper
- draw diagrams
- rewrite arguments in simpler form
effort is the signal that learning is happening.
6. separate core ideas from formalism
authors often wrap simple ideas in heavy notation.
your job:
- extract the idea
- ignore the formalism temporarily
- reintroduce math once the intuition is clear
intuition first, rigor second.
7. skip strategically, not lazily
you are allowed to skip, but consciously.
skip:
- proofs that don’t build intuition (on first pass)
- edge cases not relevant to your use
- historical commentary
never skip:
- assumptions
- constraints
- failure modes
8. convert reading into output
reading without output decays fast.
after a session:
- write a one-page summary
- explain the idea as if teaching
- implement a minimal example
- connect it to another field
output locks knowledge in place.
9. reread at higher resolution
first read builds structure.
second read builds depth.
third read builds mastery.
technical books are meant to be revisited, not consumed once.
final rule
if a technical book feels easy, you’re skimming.
if it feels slow and demanding, you’re doing it right.
read to reconstruct the author’s thinking, not to finish chapters.