How to Read
I have a problem. I feel like I have to memorize non-fiction books, which causes me to either read slow or avoid reading altogether out of fear of what I am missing.
My guess is this stems from seeing 'photographic memory' folks read something once and be able to recite it verbatim. I was always so jealous of someone who appeared like they could do this.
To (over)compensate for what I feel is a below average memory, I over highlight, take too many notes, and focus on memorizing the smallest of details. This is if I even have the energy to work this hard at reading - a lot of the time I will just avoid reading altogether out of fear of forgetting details. This is quite sad.
I need a system; a happy compromise between a thirst for information and the reality of my brain's limitations. My goal is to read non-fiction as leisure - instead of TV, I want to read. But I cannot do this with these memorization shackles tied to the activity.
To add complexity, I find if I don't highlight and take note(s) then I can often drift off while reading. I almost need an efficient way to actively synthesize while reading. Objectively, a reading system I could stick to would be something like starring key points, then highlighting a max of like 3 sentences per chapter, and/or writing a max of 3 sentences in the margin? Then at the end having 1-page summary of the whole book, focusing on concepts instead of facts?
My system for How to Read
The Filter Framework
Mindset: You are a filter, not a hard drive. Catch what changes how you think, decide, or act. Let everything else pass through. Facts are searchable. Frameworks are what you keep.
Setup
One sheet of paper, folded into the book/printed article as a bookmark.
Front:
Q: [Anchor question]
CHECKPOINTS:
1 –
2 –
3 –
...
Back:
KEY IDEAS / COMPONENTS:
1.
2.
3.
4.
5.
TRADEOFFS / LIMITATIONS:
ACTIONS / WHEN TO USE:
•
•
Anchor Questions by Type
Every author writes with a purpose. They're trying to convince you of something, explain how something works, or share what they discovered. Your anchor question cuts straight to that purpose—it's how you avoid drowning in details and stay locked onto what the author actually wants you to walk away with.
| Material type | Author's purpose | Anchor question |
|---|---|---|
| Non-fiction book | Convince you of a thesis | "What is this book arguing, and why should I believe it?" |
| Technical article/docs | Teach you how something works | "What problem does this solve and how?" |
| Research paper | Report a finding | "What's the claim, what method tested it, and what did they find?" |
| Opinion/essay | Shift your perspective | "What does the author want me to see differently?" |
| Biography/history | Illuminate through narrative | "What's the through-line, and what does it reveal?" |
Before you read a word, ask: "What is this author trying to do to my brain?" Your anchor question makes that explicit—and everything you capture should connect back to it.
The Flow
1. Scout (5-15 min)
| Non-fiction | Technical |
|---|---|
| Title, back cover, TOC, chapter openings/endings | Headings, diagrams, code blocks, intro/conclusion |
Write your anchor question at the top of your paper.
2. Read
Read at a comfortable pace. Stars go in the margin.
Max 3 stars per chapter/section. To add a 4th, remove one.
| Star this | Not this |
|---|---|
| Core claims or mechanisms | Examples, anecdotes, evidence |
| Reframes that shift your view | "That's interesting" moments |
| Actionable takeaways | Repetition of earlier ideas |
| Components and how they connect | Implementation details you can look up |
| Tradeoffs and failure modes | Syntax, boilerplate, code snippets |
3. Checkpoint (2 min, after each chapter/section)
Pull out your paper. Write one sentence.
| Non-fiction | Technical |
|---|---|
| "This chapter argued that [X] because [Y]." | "[Component/concept] does [X] by [Y]." |
Y = the reasoning:
- Mechanism ("because it works by...")
- Evidence ("because studies show...")
- Logic ("because if A, then B...")
- Reframe ("because we've been thinking about it wrong...")
4. Distill (5-10 min, after finishing)
Review checkpoints. Circle the 3-5 best. Fill in the back:
For non-fiction:
ANSWER: [1-2 sentences—author's response to your question]
KEY IDEAS:
1.
2.
3.
ACTIONS: [What will you do differently?]
For technical:
PROBLEM: [What does this solve?]
MECHANISM: [How does it work, in one sentence?]
COMPONENTS:
1.
2.
3.
TRADEOFFS: [Where does it fail? What are the costs?]
WHEN TO USE: [What situations call for this?]
Photo the sheet. File it. Done.
Optional: Spaced Repetition (≤10 cards, skeleton only)
| Card type | Non-fiction example | Technical example |
|---|---|---|
| Core question/answer | "What's the main argument of [book]?" | "What problem does [X] solve?" |
| Key idea / component | "What does [concept] mean?" | "What does [component] do?" |
| Application | "When would I use this insight?" | "When would I use [X] over [Y]?" |
| Tradeoff/failure | "Where does this argument break down?" | "When does [X] fail?" |
No fact cards. No trivia. No implementation details.
If you want more than 10 cards, stop. That's the old pattern.
The Shift
| Old | New |
|---|---|
| Everything is important | Most is forgettable |
| I must memorize | I must filter |
| My brain is storage | My one-page summary is storage |
| Forgetting = failure | Forgetting = working as intended |
| I want to be an encyclopedia | I want to be a thinker |
| I memorize how it works | I know when and why to use it |
A book succeeds if you think, decide, or act even 1% differently.
An article succeeds if you know when to reach for it and what tradeoffs to expect.
Store the skeleton. Let the flesh be searchable.