Why tutorials don't stick, and what to do instead

You watch the video. Every line makes sense. The instructor is clear, the project builds, and at the end you have a working app on your screen. Then you open a blank file the next morning and cannot write the first line.

This is so common that people assume it is a personal failing. It is not. It is a predictable result of how the material was structured.

Recognition is not recall

When you read code someone else wrote, your brain does something easy: it checks whether the code looks familiar. That feeling of "yes, I understand this" is recognition, and it arrives almost for free.

Writing code from scratch needs something much harder: recall. You have to retrieve the shape of the solution without anything on screen to prompt you.

The two feel similar from the inside, which is the whole problem. A tutorial that flows smoothly generates constant recognition and almost no recall, so you finish it feeling like you learned a lot while having practised nothing.

The fluency illusion

There is a well-documented effect in learning research: the easier material feels while you study it, the worse you tend to retain it. Difficulty during practice is not a sign that something has gone wrong. It is usually the thing doing the work.

This is why re-reading your notes feels productive and rarely is, and why struggling to remember something for thirty seconds before getting it does more for you than reading the answer four times.

What actually helps

Three changes, in rough order of how much they matter.

Close the tutorial before you type

After a concept is explained, shut the tab and write the example yourself. You will get it wrong. Getting it wrong and then finding out why is the entire mechanism — you cannot skip to the part where you know it.

Answer questions you might get wrong

A question you are certain about teaches you nothing. The useful ones are the ones where you have to stop and think, and where being wrong tells you something specific about your model of how the language works.

This is why every lesson here ends with a quiz, and why the next lesson stays shut until you pass it. Not to be strict — to stop you carrying a misunderstanding forward into material that builds on it.

Come back tomorrow

Spacing your practice out beats cramming so reliably that it is one of the few things in learning science nobody argues about. Twenty minutes a day for a week will leave you with more than one long Saturday session.

The streak on your dashboard is there for exactly this reason. It is not a gimmick — showing up on more days is genuinely the highest-leverage thing you can change.

What to remember

• Understanding an explanation and being able to produce the code are different skills, and only one of them is trained by watching.
• If practice feels easy, it is probably not doing much.
• Write it yourself, test yourself, and come back tomorrow.

None of this is complicated. It is just slower and less comfortable than watching someone else be competent, which is why so few people do it.