Why You Remember Nothing You Learned From a Tutorial

I finished a nineteen hour course on SQL in eleven days. Three weeks later I could not write a join without a second tab open, and I had a certificate saying otherwise. I did that four more times before I admitted there was a pattern.

Following along feels exactly like learning. That is the whole problem, and it is why the pattern survived five repetitions before I noticed it.

The ceiling

Every tutorial sets a ceiling on what you can take out of it, and the ceiling is set by the thing it removes. The job of a tutorial is to take out the part where you are stuck. It anticipates the error before you make it, names the file before you name it wrong, and hands you the next step at the exact moment you would otherwise have to guess.

That guess is the mechanism. The memory does not form while you watch the correct move. It forms while you try to retrieve the correct move and fail, and a tutorial is engineered to prevent the only event that encodes anything.

Call it the tutorial ceiling. The diagnostic takes ten minutes: open a blank file and rebuild the last thing a tutorial walked you through, no tabs, no notes. Count the seconds before you reach for something. If the answer is under thirty, you did not learn it, you watched it.

What I noticed

I moved to a city where I did not drive for the first year. A friend took me to the same trailhead maybe a dozen times. The first morning I drove myself I missed the exit, then missed the correction, and ended up at a gas station forty minutes from a place I had been to twelve times.

The passenger sees everything the driver sees. Same road, same turns, same signs, and better views, because the passenger is not watching mirrors. What the passenger never does is predict. The driver has to commit to a turn before the sign confirms it, and being wrong at fifty miles an hour is what builds the map. Twelve trips of excellent visual data produced nothing in my head, because none of it ever cost me anything to retrieve.

What I run now

Any tutorial I open gets watched once, all the way through, hands nowhere near the keyboard. Then it closes and I build the thing badly from blank for forty minutes.

Forty minutes is not enough time to succeed. It is enough time to fail in specific places, and the specific places are the entire product. When the forty minutes end I am allowed back in, but only to answer a question I can already state in one sentence. If I cannot state the question, I have not been stuck long enough to have earned one.

Results so far

Nine things have gone through this since January. Five I can now do from blank, which is five more than the nineteen hour course produced. Two I half have, and I keep looking up the same argument order every time, which is honest information about what I actually practiced. Two I abandoned inside the first forty minutes, because failing at something for forty minutes is a very fast way to find out you do not want it.

It is also slower. The course took eleven days and left nothing. The same material done this way took six weeks. I have stopped filing that as a drawback and started filing it as the price.

The certificate was accurate. I did complete the course, on time, at speed, every module marked green. Completing was never the thing I was trying to buy, and it took five certificates to notice I kept buying it anyway. You have been riding shotgun through material you can describe perfectly and cannot drive. Close the tab, take the wrong exit, sit at the gas station for a while. That part is the map. [1]

[1] The uncomfortable corollary: the tutorial market is stable because it sells a sensation rather than a skill, and the sensation is available on demand, in higher quality, at a lower price than the real thing.