← Back to overview

how to read, especially books

> Don’t read this book for its content; read its content for its practices.

β€” πŸ“– Praying Like Monks, Living Like Fools

also: always look for applications

⁓ well-used systems naturally grow complex

a meta observation, definitely (at least at times) see that in my "reading system"

~ reading too fast or too slow is harmful

Pascal observed three hundred years ago, β€œWhen we read too fast or too slowly, we understand nothing.”

β€” πŸ“– How to Read a Book

sounds like Goldilocks principle

~ read quickly by reading a lot about a topic

The basic principle is easy to grok: once you’ve read enough books about a single topic, it becomes trivially easy to read a new book on that topic. This experience should be familiar to computer programmers: for every n programming language you know, the n+1 programming language you adopt becomes easier to learn

β€” Reading Quickly is Reading a Lot

(great post to re-read in general)

~ note-taking while reading interrupts flow

~ read a page of a book, close the book, write down what you remember

β€” The Best Learning Tool in History - 400 years ahead of its time!

  • well this only works if the book is really that good...(or/and you care that much about every detail)