Why typing along teaches nothing

1. The split

When you type along with a tutorial, two things are learning — and they are not the same thing.

Your fingers are learning the muscle memory of typing certain characters in certain orders. They will get faster at it.

Your brain is learning, optionally, why those characters are in that order. Whether it learns this depends entirely on whether your brain had to do any work to produce them — and during type-along, it didn't.

What you walk away with is finger memory for code you cannot reason about. This is exactly the wrong direction.

2. The way the brain encodes

Memory consolidates around effort. Specifically, around the moment of retrieval — the moment you tried to produce something from inside your head and either succeeded or failed.

Typing what you can see is not retrieval. It is transcription. The brain does not flag transcription as important. It treats it the way it treats copying a phone number off a screen: useful for the next thirty seconds, gone by tomorrow.

Closing the source and writing the same thing from scratch is retrieval. The brain treats that as important and stores it. The two activities look similar from the outside. They are different worlds inside your head.

3. Try it

This one needs no preparation. Pick the last block of code you typed from a tutorial — twenty lines or so, something you "understood" while writing it.

Close the tutorial. Open a blank file. Try to recreate it from memory.

If you nailed it, your fingers and your brain were both engaged the first time. Good. If you didn't, that's normal. The gap is the lesson, and the lesson is free now that you know it's there.

4. The correction

When you watch a tutorial, watch. When the section ends, close the materials and rebuild from scratch — not the same thing, but something like it, with your own small variation.

That single change turns a passive activity into a real one. It will feel slow. It is not slow; it is the first time learning has actually been happening.