Every programming language has a 700-page book. JavaScript has several. TypeScript has one. Even CSS has one, somehow. And at some point, every developer has bought one, read the first three chapters, and never touched it again.
I've done this more times than I want to admit. The book sits on my desk looking impressive. I tell myself I'll get back to it. I don't. And then I feel guilty about it, like I'm not serious enough about learning.
But here's what I eventually realized: the problem isn't discipline. The problem is that 700-page books aren't learning tools. They're reference material disguised as learning material. And that matters.
Why They're So Long
A 700-page JavaScript book covers every edge case, every browser quirk, every historical API that nobody uses anymore but technically still exists. It explains var and let and const and why all three exist. It has a chapter on with statements. It covers arguments objects and caller properties and prototype chains going back to 1995.
That's not padding. It's completeness. The book is trying to be the definitive resource on the topic. And for that purpose, it works. If you need to know some obscure behavior of Object.defineProperty, the book has it.
But completeness and learnability are different goals. They often work against each other.
Here's why these books end up so long:
Audience breadth. The book serves beginners who don't know what a variable is AND intermediates who want to understand the event loop. It can't assume what you know, so it explains everything. A condensed resource picks a level and stays there.
Defensive writing. Authors anticipate every possible misunderstanding. "You might think X, but actually Y. Don't confuse this with Z. Note that in older browsers, this behaves differently." Each caveat adds a paragraph. Each paragraph adds a page.
Examples as repetition. Good books show the same concept in five different contexts. Closures in callbacks, in factory functions, in event handlers, in module patterns, in React hooks. The idea is that one of these will click for you. A condensed resource shows it once or twice and trusts practice to do the rest.
Perceived value. Nobody pays $50 for a 40-page book. The market rewards volume. That's not cynical, it's just how publishing works.
The Signal-to-Noise Problem
A 700-page book and a condensed course can contain the same core knowledge. What changes is the signal-to-noise ratio.
The book wraps each concept in context, history, caveats, transitions, and gentle hand-holding. The condensed version strips that away and gives you the concept raw. Both have their place.
But for actual learning, for building knowledge that you can recall and use, the condensed version wins. And it's not close.
Here's why: when you forget something six months from now (and you will, that's how memory works), you need to re-learn it. With a 700-page book, re-learning means finding the right chapter, skimming past the parts you remember, trying to locate the specific thing you forgot. It takes 30 minutes and you probably give up and just Google it instead.
With condensed material, re-learning means reading a 2-minute lesson and taking a quick quiz. The barrier is so low that you actually do it. And that matters more than anything, because the best learning system in the world is useless if it's too much effort to actually use.
The Forgetting Curve Isn't Your Enemy
You will forget things. I forget things constantly. I've written TypeScript for years and I still blank on the exact syntax for mapped types sometimes. That's not a failure. That's normal.
The question isn't how to prevent forgetting. It's how to make re-learning fast.
After your first exposure to a concept, re-learning takes about 70% of the original time. After the second cycle, maybe 40%. After the third, 10%. Each round of forgetting and re-learning makes the knowledge stronger and the recovery faster.
This is why the format of your learning material matters so much. If re-learning is quick and easy to start, you'll actually do it. If it means cracking open a 700-page book, you won't. You'll just ask an LLM and move on, which solves the immediate problem but doesn't build lasting knowledge.
What This Means for How You Study
It comes down to this: optimize for re-learning speed, not first-time completeness.
A learning system should be:
- Condensed. Strip the filler. Keep the concept. If you can explain closures in 200 words instead of 2000, do it.
- Reviewable. You should be able to re-read a lesson in 2-3 minutes, not 30.
- Testable. Quizzes after each concept, so you know what stuck and what didn't. Not as assessment, as learning. The quiz IS the learning (as I wrote about earlier).
- Repeatable. Going through the same material multiple times should feel natural, not tedious. Each pass is faster and reveals connections you missed before.
The 700-page book has its place. It's a great reference. It's useful for a deep first encounter when you need multiple angles on a confusing topic. Keep it on your shelf.
But for building knowledge that actually sticks? Give me the short version and a quiz. I'll remember more from 10 minutes of that than from 3 hours of reading a chapter I'll never revisit.
This is part 3 of a series on effective learning. Previous: The Multimedia Myth