Tutorial Hell

A simple explanation

You have completed eleven tutorials, two full courses, and three project walkthroughs. You can follow along with almost any new framework introduction. You have shipped exactly zero things that were not already mapped out for you to copy. The moment the video stops and the blank file opens, something in you stalls. You go back to the next tutorial.

Tutorial hell is the gap between guided execution and unscaffolded creation, run as a long-term substitution. The guided side keeps producing wins. The unscaffolded side keeps not happening. Over time the gap widens, not narrows.

An everyday example

A weekend. You set aside the morning to finally build the small project you have been planning. You open the editor and create a new file. The blank screen is there. Two minutes pass. You realise you are not sure how you would structure the routing, even though you watched a routing tutorial last week. You decide you should refresh your memory. You open the tutorial, follow along for forty-five minutes, finish the example app, feel competent and warmed up, and look at the clock.

It is now 1 p.m. The morning is gone. The original project still has an empty file. You feel productive — you did, after all, do something with code. You also feel a quieter thing underneath, which you do not name: the original project did not advance, and a small voice has noticed.

How do I escape tutorial hell?

You stop adding tutorials and start building, badly. The badly is the point. The gap between tutorial and project is not a knowledge gap; it is an experience gap with starting under uncertainty. The only way to close it is to start under uncertainty repeatedly, at a quality level that would horrify the version of you that finished those eleven tutorials.

The Meaning System will resist this hard. Tutorials offer clean wins; bad first builds offer messy half-wins. The System is calibrated to prefer the clean. The work is to teach it that the messy half-wins are the only ones that actually move the underlying capacity.

The behavioral loop

A loop that hides because each iteration produces a real, demonstrable artefact:

1. Capability ambition — a clear felt-pull toward becoming someone who can build X.
2. Tutorial discovery — a high-quality walkthrough is found. It is genuinely well-made.
3. Following phase — focused, satisfying work. The mind is engaged. The code compiles. The output appears.
4. Completion signal — the tutorial ends; the example app works. A clean reward arrives. The System logs progress.
5. Application attempt — at some later point, a blank file is opened. The pull toward the next tutorial appears almost immediately.
6. Substitution event — the next tutorial is chosen, often justified by I need to learn one more thing before starting. The blank file is closed.
7. Library accumulation — the tutorial history grows. The portfolio does not.
8. Quiet gap-widening — the gap between guided and unscaffolded ability does not shrink because the unscaffolded side is never exercised.

Emotional drivers

Four feelings, often unnamed:

• A specific anxiety about beginning under uncertainty — the discomfort of not knowing what the next line should be — which the System classifies as a knowledge deficit rather than as a starting one.
• The clean satisfaction of guided execution, which the Reward System reads as competence and which is genuinely pleasant.
• A faint, growing dread about the portfolio gap, often managed by working on the next tutorial rather than by facing the blank file.
• A specific imposter-flavoured shame that activates when others reference what they have built, which tends to be answered by buying or queuing more tutorials.

What your nervous system does

Following a tutorial is a flow-state-adjacent experience: directed attention, manageable challenge, clear feedback, real reward at completion. The body settles into a productive, satisfied mode. Opening a blank file produces the opposite pattern: directional uncertainty, no clear next move, no scaffolded feedback. The Threat System flags the uncertainty as exposure. The Reward System, getting no clean hit signal, withdraws engagement.

Over months and years, the comfort threshold drifts toward guided work and away from blank files. The somatic response to the empty editor strengthens. People in tutorial hell often report a specific, physical heaviness at the moment of starting that does not appear when the tutorial is loaded.

The DojoWell interpretation

Tutorial hell is one of the cleanest false_progress patterns in modern technical learning. The Meaning System's ask was a real capability: to become someone who builds. The substitute on offer is guided execution, which produces a measurable output that looks, from outside, like building. The two are not the same activity. Following a tutorial is closer to playing a guided puzzle game than to building from intention. The puzzle game is satisfying. It also does not transfer to puzzles you have to design yourself.

The MDT equation reads it cleanly. The effort term is high — many real hours of focused work. The deposit term is low because the part of capability that is actually being asked for — the ability to start under uncertainty, to make decisions without scaffolding, to recover from being stuck without a video to consult — is the specific part the tutorial is not exercising. The residue term accumulates as a felt-gap between apparent and actual ability, surfacing every time the scaffold is removed. Density is low.

The signature is false_progress because the System logs a clean win at the end of every tutorial. The win is real on its own terms; the failure is that the win does not generalise. The closure pattern is substituted: tutorial completion takes the place of the building moment so reliably that, in many cases, the original ambition stops getting tested at all.

The deeper read is what the substitute reveals about the original ask. Building under uncertainty is hard in a specific way: it requires sitting with not-knowing, making decisions without confirmation, and shipping something that will be visibly imperfect. Each of these activates a different System — Threat, Meaning, Belonging — and each System has a vote. The tutorial substitute satisfies all of them at once. It is not laziness that keeps the pattern in place; it is the unusual convergence of three System preferences on a single behaviour.

Resolution is not abandoning tutorials. Tutorials are excellent for specific learning. Resolution is structurally separating the tutorial mode from the building mode in time, so the gap can be exercised under low stakes and progressively closed.

When do I stop watching and start building?

Three moves.

1. Cap tutorials at one per project. Pick a small project. Choose one tutorial that covers the core technique. Do that tutorial. Then start the project. No further tutorial until the first version ships.
2. Use the bad-first-version rule. The first version of the project must be visible to at least one other person within seven days of starting, regardless of quality. The deadline pressures the System into letting the blank file get filled.
3. Stuck = ten minutes, then ask, not search. When stuck, attempt for ten minutes, then ask a human or post in a community. Searching for another tutorial when stuck is the relapse path. The pattern is to make humans, not videos, the resource of choice.

Practical steps

1. Inventory the tutorial-to-build ratio. For the last six months, count tutorials completed and projects shipped from scratch. The ratio is the diagnostic.
2. Pick a tiny project below your current tutorial level. Not a stretch project — a project clearly inside the skills you already have on paper. The point is to exercise starting, not to acquire new skills.
3. Ship one ugly thing this month. Public. Imperfect. Yours. The ugliness is the deposit. Polish will come later; starting won't, unless this happens.
4. Replace half your tutorial time with build time. Not eliminate tutorials — replace. If your current ratio is ten hours of tutorial to zero hours of building, target eight hours of each, then six and four, then four and six.
5. Find one builder community over one tutorial community. Communities calibrated around shipping work — even small work — pull the system toward action. Tutorial-centred communities reinforce the loop.

Reflection questions

• When was the last time you started a project without a tutorial to follow, and what happened?
• Which step of building actually freezes you — the structure, the first line, the decisions, the visibility?
• What would change if your portfolio had three small, ugly, unguided projects instead of eleven polished tutorial replicas?
• Whose judgement are you avoiding by staying in tutorial mode?

Frequently Asked Questions