Comprehension Requires Your Own Words

Reading is deceptive. A well-written book is designed to be easy to follow, because the author has done the thinking for you. You nod along, every sentence makes sense, and a week later you can’t explain any of it. Following along isn’t understanding.

The test

To really understand an idea, you have to be able to state it in your own words, without the book open. Even better, explain it to someone else. Gaps show up immediately: the step you can’t justify, the term you can’t define, the example you can’t come up with.

Writing is a great way to put pressure on your thinking: it’s hard to summarise something you don’t sharply understand. — Andy Matuschak (paraphrased)

How I practise it

• Every definition gets rewritten. Reading a dense technical book, I note each definition and then write my own version. If I can’t, I don’t understand it yet. Then I review my version later, not the author’s.
• Notes without quotes. Copy-paste is allowed only for the reference. Everything else is paraphrase. That’s the core rule of literature notes.
• Teach it. Plan how you’d explain the idea to a colleague, or write a short post. Publishing raises the bar further. That’s part of why this garden exists.

A worked example

Take FLP Impossibility. The textbook statement is about deterministic algorithms in asynchronous systems with one faulty process. My own words: you can’t tell a slow node from a dead one, so you can’t guarantee a group will ever finish agreeing. It’s less precise, but now I can use it in a design review, and I can tell when someone’s timeout is really a guess.

The trade-off

Paraphrasing is slower than highlighting, and your own words can be wrong. That’s fine. A wrong explanation you wrote can be corrected; a highlight you never thought about can’t. Pair it with Spaced Repetition so the corrected version sticks, and with The Second Brain so it’s there when you need it.