You read three articles about a new topic, and at first you may feel like you understand it. Yet when someone asks you to explain it, you stumble. Not because you forgot what you read, but because reading and understanding are different things. The information is still there in pieces; you just never assembled it into anything coherent.

Accumulating information isn’t the same as understanding it. Understanding means finding the pattern underneath the details, distilling a verbose mass of facts into something you can hold in your head and work with. That distillation is what separates someone who has read about a subject from someone who actually knows it.

You can see this in how different skill levels explain the same concept. A novice oversimplifies because they haven’t encountered the complexity yet. An intermediate developer recites every detail because they’ve accumulated facts without organizing them. The expert knows more than either, but they’ve compressed that knowledge into fewer, more powerful concepts. They aren’t skipping details; they’ve internalized them deeply enough to regenerate them from fundamentals.

Compression isn't eliminating details. It's internalizing them deeply enough to regenerate them from fundamentals.

Compression requires depth first, and the act of compressing always reveals new gaps. Each time you distill what you’ve learned, you discover more specific things you don’t yet understand. The process is cyclical, and it starts not simply with study but with recognizing what you don’t know.

The Cycle

Ignorance → Expansion → Compression → New Ignorance → Repeat.

It starts with noticing a specific gap. Not “I don’t know Rust” but “I don’t understand how Rust’s borrow checker prevents data races without garbage collection.” Generic ignorance doesn’t guide research; specific ignorance does. So the first move is articulating what you actually don’t know, precisely enough to research it.

Then you go deep. You read and study and accumulate detail. The information gets overwhelming, and that’s fine. You need the complexity before you can compress it. Trying to summarize prematurely, before you’ve seen enough of the landscape, just produces a different kind of oversimplification.

Compression happens when you try to teach what you’ve learned. Teaching forces externalization; you have to convert internal, half-formed understanding into something another person can follow. When your explanation turns verbose, the pattern isn’t clear yet. When you reach for jargon, you’re avoiding precision rather than achieving it. But when you can explain something briefly while maintaining accuracy, that’s when you actually understand it.

Teaching and writing compress differently. Face-to-face, confused looks and follow-up questions reveal gaps in real time. Writing demands that you anticipate those questions without feedback. Both are useful, and they complement each other. Teaching reveals what you can’t explain under pressure, while writing reveals what you can’t structure without help.

Teaching reveals new ignorance, like questions you couldn’t answer, edge cases you hadn’t considered, and connections you hadn’t made. This new ignorance is more specific than where you started because it’s informed by the depth you just explored. It becomes the next cycle’s starting point, and each iteration produces tighter understanding and more targeted questions.

Why This Accelerates Learning

Learning isn’t accumulation; it’s expansion followed by compression. Most people get stuck in expansion, accumulating facts without compressing them. Others try to compress prematurely, building understanding on incomplete research. Both approaches skip the critical interplay between depth and distillation.

The cycle forces deliberate progression through each phase. You acknowledge specific ignorance, expand through deep research, compress through teaching, and discover new ignorance that’s more refined than where you started. Each iteration produces tighter compression and reveals more targeted gaps.

This is how experts explain simply. Not because they know less, but because they researched deeply and then compressed ruthlessly. The simplicity you admire is the output of multiple cycles, each round refining both what they know and what they know they don’t.