(“Ask HN: How Do You Learn Complex, Dense Technical Information?” n.d.)


Relevant: How to Read a Paper


Essentially I think learning is fundamentally Pain. You have to take on the pain before the learning can alleviate it, if you try to skip the pain then you have only a superficial idea of what you’re talking about.


Interestingly there is a concept in learning research called “desirable difficulty”. The idea is that learning something, forgetting it and then struggling to learn it again leads to faster learning times. It may be that struggle is inherent in the process of learning something complex. If you equate struggle with pain, then I think it makes some sense.


In my ~20 years of experience, the only way to get good at something that is incredibly complex like kernel development, you will need to actually try to build the thing. Over and over and over.


In the language learning example, Extensive Reading leads to not only picking up and remembering words, but also collocations, grammar and even cultural beliefs of the speakers of the target language. Single word flash cards miss all of that. Full sentence flashcards do a bit better but still fall short.

I think the best use for SRS for something like a language or programming is for laying down a scaffold in the very early stages of learning, and then moving to more productive uses of study time as soon as possible.

AlchemistCamp, replying to stared

This raises an important point in the use of spaced repetition systems (SRS). I wouldn’t expect someone to be able to write a good essay if they only studied the meaning of words. Spaced repetition systems lend themselves easily to the study of small chunks of information (eg: definitions) but it is more difficult to apply them to higher-level applications of knowledge and understanding (eg: essay writing).

I think semantic tree/first principles/physics-based approach (popularly attributed to Elon Musk) is one way to approach it. It’s actually a really difficult approach and you need a certain level of intelligence and personality to do it well, so it’s not for everyone. I can do it to some extent but it’s actually really difficult to hold lots of ideas in tension and to be questioning all the time – it’s just not my thinking style.

The other approach is what many smart (but non-geniuses) take: the buffet approach. You graze at the table of books, Wikipedia, online articles, and hang out in online communities (like Twitter) to overhear what experts are discussing. The thing about most areas of knowledge is, there’s usually only 20% of the subject that matters–the rest rarely come up (Pareto Principle). To know what 20% to focus on, you need to understand the sociology of the subject matter and what experts think are important. Unlike the previous approach, you won’t have watershed-level insights, but you’ll know enough to be considered “educated” on the subject.



“Ask HN: How Do You Learn Complex, Dense Technical Information?” n.d. Hacker News. Accessed February 6, 2022. https://news.ycombinator.com/item?id=22325975.