Tutorial Hell: Why You Can Follow Anything and Build Nothing

What it actually looks like

You can follow anything. Put a course in front of you and you keep pace, catch the mistakes before they are corrected, and finish the module with working code on the screen. You are not pretending. In that context you are genuinely good.

Then you open an empty file for your own project, and there is nothing. Not confusion — a kind of blankness. You do not know where the first line goes. Ten minutes later you are watching something instead, and the relief when the video starts is instant and physical.

You have built the same small app four times in four frameworks. Each time it worked. Each time you thought: now I understand it. Each time the understanding did not survive contact with an idea that was yours.

Your notes are immaculate. Folders, tags, diagrams, a summary of every module. You have never gone back to them.

The prerequisite list has never got shorter. It used to be one language. Then a framework, then the database part, then the deployment part, then the type system, and now something about architecture that you saw in a thread and cannot yet name properly.

And you have been "almost ready to start" for a while. You would have to think to say how long, and you notice that you do not want to.

Who this happens to

This is common among self-taught developers and people who moved into tech from somewhere else.

Nobody ever handed you a document saying you were qualified. Someone who came through a degree got that piece of paper, and whatever else it did, it ended a question. Without it, you keep looking for the moment when you will be allowed to consider yourself ready — and courses are the only thing in the world that hands you a completion certificate for finishing something.

It is common in people who were good at school. Guided learning is a game you have won before: someone sets the syllabus, you work hard, you are graded, you do well. Building your own thing is a game with no syllabus, no grade, and nobody confirming you are on track. Going back to the format where you have a proven record is not weakness. It is a sensible move, made by a part of you that is trying to keep you feeling capable.

And it happens to people who are afraid of building it wrong — which usually means people who have read enough to know how many ways there are to be wrong. The more you have learned, the longer the list of mistakes you can now imagine making, and the more reasonable it feels to learn a little more before risking one.

What sets it off

The blank file sets it off, every time, and faster than you can observe.

A perceived gap sets it off. You read a job description, or a thread where four people discuss something you have never used, and the ground drops slightly. The natural response is to close the gap, and closing gaps by studying is a thing you know exactly how to do.

A new framework release sets it off, because it is the most legitimate-looking reason available to go back to lesson one. Everyone is starting from zero on this one. There is no shame in the beginner's seat when the thing itself is new.

And the sharpest trigger is getting stuck on your own project for the first time. You hit a problem the tutorials never covered, sit with it for twenty minutes, and a sentence arrives fully formed: I do not know enough yet. That sentence feels like a diagnosis. It is the moment the whole pattern turns around, and it happens somewhere quiet, with nobody there to argue.

Why it keeps happening

The mechanism is that watching a competent person produces the feeling of competence without the thing itself.

When an instructor works through a problem smoothly, you follow every step and each one makes sense. Your brain registers that: I understand this. And you do — you understand it in the sense of recognising it when it goes past. Recognition and production are different capacities, and they feel identical from the inside. This is why the gap between "I followed that easily" and "I cannot start" is so shocking every time, and why it never quite gets believed.

The deeper issue is what the tutorial has already done for you before you arrive. Someone chose what to build. Someone decided the order, the file structure, the names, where to put the boundary between one piece and another, what to do when it did not work the first time. All of that was removed before the recording started — and all of that is the skill. What is left for you to practise is typing, comprehension, and following. You have got extremely good at the three parts that were never the hard part.

Then the incentives lock it in. A course pays out constantly: a progress bar, a green test, a module completed, a small legitimate sense of moving forward every twenty minutes. It also never rejects you and never leaves you stuck, because someone removed the stuck parts in the edit. Your own project pays nothing for two hours and then hands you an error you have never seen. Set those side by side and the pull is not mysterious.

And underneath all of it is one mislabel doing most of the damage. Being stuck is not evidence that you are not ready. Being stuck is the mechanism — the thing that actually builds the capacity, the friction where a solution you generated yourself gets written somewhere durable. You have been treating the lesson as proof that you should go back to studying, which is the one response that guarantees the pattern continues.

The prerequisite list is also infinite by construction. There is always another layer, and there is no version of you that has learned enough, because "enough" is defined by a feeling that studying does not produce.

What actually helps

Build something ugly today, from an empty file, and keep it small enough to finish this evening. Not a portfolio piece. A script that renames your files, a page that shows one number you care about, a tool with one button. The requirement is not that it is impressive. The requirement is that nobody told you how to structure it, so that you are practising the part you have never practised.

Search only when you are blocked, and only for the specific block. No videos, no "let me refresh my understanding of" — the exact error, the exact function, the smallest possible question. Then close the tab and go back. This one rule is the whole difference between using material as a reference and using it as shelter.

Make consumption the reward for production rather than the preparation for it. Nothing gets watched until you have written something of your own that day. It is a crude rule and it works, because the sequence is what has been backwards, not the appetite.

Rebuild a tutorial project from memory, with the video closed. You will fail somewhere in the first ten minutes, and where you fail is the honest picture of what you actually know. That gap is not a verdict. It is a list, and it is far shorter and far more specific than the vague, endless one you have been carrying.

And when the stuck feeling arrives, name it out loud: this is the part where the learning happens. You are not going to feel ready, and it is worth stopping waiting for that. Readiness is produced by having built things badly, several times, and noticing afterwards that you can now do something you could not do in March.