What explanation cannot teach

You can read every explanation of how to ride a bicycle and fall off. Nobody finds that surprising.

The same is true of a great many things people do try to learn by reading, and it is worth naming which.

Knowing how and being able to

Two different kinds of knowledge.

Knowing how it works — the concepts, the principles, the vocabulary. This is what explanation delivers, and everything up to L6 was about acquiring it efficiently.

Being able to do it — judgement built from repetition. Knowing which approach fits this case, noticing when something is off, recovering when it goes wrong.

The second is built by doing the thing and getting feedback, repeatedly, and there is no substitute. It is not stored as facts and cannot be transferred as explanation.

Where this catches people

Skills that feel learnable by reading and are not:

Writing. You can know every principle in E5 and write badly. Writing is improved by writing and being read.

Diagnosis — medical, mechanical, technical. Pattern recognition built from having seen many cases, including the ones that looked like something else.

Conversation — negotiation, interviewing, teaching, difficult conversations. E9·L7’s rehearsal exists precisely because reading about it does nothing.

Craft and physical skill. Cooking, playing an instrument, sport, surgery, carpentry.

Design and taste. Recognising that something is not working yet, which is built from having made many things that were not working.

Code. You can follow every explanation and be unable to build the thing.

Common thread: the knowledge lives in your reactions, and reactions are trained by exposure rather than told.

The trap this module could create

Everything before this lesson made acquiring explanations more efficient. That efficiency creates a specific risk.

Reading feels productive. It is comfortable, it is measurable — pages, videos, lessons — and it produces the fluency L1 warned about. So it is very easy to spend six months efficiently learning about something and never once doing it.

That is worse than inefficient. It builds the confident, articulate half-knowledge that E8·L1 warned about: you can discuss it and you cannot do it, and you will not find out until it matters.

Where an assistant genuinely helps

Around the loop, not inside it:

Designing practice. “I want to get better at X. Give me five exercises, increasing in difficulty, that I can do this week.”

Generating cases. Unlimited practice scenarios, examples to diagnose, prompts to respond to. This is real value — cases used to be the scarce thing.

Reviewing an attempt. E5·L3’s critique, applied to work you produced. Specific objections, no praise.

Explaining the failure. After you have tried and it went wrong, an explanation of why lands in a way the same explanation beforehand would not. The attempt creates the hook.

Rehearsal, per E9·L7, for conversational skills.

What it cannot do is the repetition. Nobody can do that part for you, which is the whole reason it works.

The order that works

Explanation first, briefly. Enough to attempt it — not everything.

Attempt it. Badly. Early.

Get feedback. From the assistant, a person, or reality.

Then explanation again, targeted at what went wrong.

Most people invert the first two and spend the majority of their time in step one, where it is comfortable.

Try it now (6 minutes)

Pick a skill you have been reading about rather than doing.

Ask for five exercises, increasing in difficulty. Do the first one now, badly. Then ask for critique on what you produced.

Check your understanding

1. Skills like writing, diagnosis and design cannot be learned by explanation because: They are too complex to explain The knowledge lives in trained reactions built by repetition and feedback Explanations of them are usually poor

2. The specific risk this module creates: Learning too many facts Spending months efficiently learning about something and never doing it Relying on flashcards

3. Why does an explanation land better after a failed attempt? You are more motivated The attempt creates a hook the explanation can attach to You read more carefully when frustrated

Recap

Knowing how something works and being able to do it are different, and the second is built only by doing and getting feedback. Writing, diagnosis, conversation, craft, design and code all fall in that category. Use an assistant around the practice loop — designing it, generating cases, critiquing attempts, explaining failures — and never in place of the repetition. Explain briefly, attempt early, then explain again.