Why am I stuck in tutorial hell?

A good tutorial is a demonstration of somebody else's finished decisions. By the time you meet it, the hardest work is already done and invisible: what to build, what to leave out, which error was worth chasing, which library to reach for, and what to do when the screen says something unexpected.

Following along exercises typing, reading and comprehension. It does not exercise choosing — and choosing is what a blank file actually asks for. This is why the gap feels so sudden. It is not that you forgot the material; it is that you never practised the part that is missing.

Because it feels smooth, and smoothness is the signal we mistake for progress. Material you have just watched someone explain is maximally familiar, and familiarity is nearly indistinguishable from competence from the inside.

The study-techniques literature is unusually blunt about this: rereading and highlighting — the passive, comfortable strategies — come out with surprisingly low utility, while practice testing and spacing come out as the two that reliably work across ages and abilities.¹ Watching a tutorial is rereading with better production values. It is the most pleasant thing on that list and close to the least effective.

Effortful retrieval is the mechanism, and it is unpleasant by design.² The research programme around this even has a name for it — desirable difficulties, the conditions that slow you down while you learn and leave more behind afterwards.³ If a study session feels good the whole way through, that is information about the session.

The usual advice is "build your own project", which is correct and is almost useless, because the reason you are stuck is that choosing a project is the skill you have not practised. Told to build something, most people pick something four times too large, stall, and go back to tutorials — reasonably, because the tutorial was the thing that was working.

Make the first one absurdly small. One function. One query. One page. Small enough that the only hard part is the part you are trying to practise, and short enough that finishing it is not a matter of stamina.

A brief here states the problem, publishes the checklist it will be marked against, and stops. No worked solution, because a worked solution is the tutorial again — and the whole point is the interval between reading the problem and knowing what to do, which is the part a walkthrough deletes.

There are 22 briefs across 7 subjects, all readable without an account, all with their bands published in full — 3 of them in Python across 17 skills. Tutorials are still useful, and you should still read the documentation; the difference is what happens after.