STR Coding Club logo STR Coding ClubLearn to code, together
First Steps

How to Escape Tutorial Hell and Build Something Real

One of our club members turned up last autumn having watched roughly sixty hours of Python video across four months. He could explain what a dictionary was, what a list comprehension did, and why you might use a class.

A beginner sitting in front of an empty code editor with a paused video course open on a second screen

One of our club members turned up last autumn having watched roughly sixty hours of Python video across four months. He could explain what a dictionary was, what a list comprehension did, and why you might use a class. I asked him to write a program that counted how many times each word appeared in a paragraph. He opened a blank file, typed the word import, deleted it, and sat there for eleven minutes. Then he said he probably needed to redo the section on dictionaries.

He did not need to redo anything. He had watched someone else solve problems sixty times and had solved nothing himself, and the gap between those two is not filled by more watching. I see a version of this in every intake, usually in the people who are most conscientious about studying, and the name that has stuck for it online is tutorial hell. The thing that gets missed is that it is a planning failure rather than a motivation failure, and it has a fairly mechanical way out.

What is actually missing

Three separate skills get bundled together and called learning to code. The first is comprehension: following a solution and understanding why each line is there. Tutorials train this extremely well. The second is recall: producing the syntax from memory without a reference open. The third is what I would call production, which is deciding what to build next when nobody has told you.

Tutorials train the first and touch the second by accident. They cannot train the third at all, because the whole format depends on somebody else having already decided. A course where every decision is made for you is a course where you never practise deciding, and that is the skill that turns out to carry the actual difficulty.

This is why the feeling is so disorienting. The learner is genuinely improving at the thing being measured, which is understanding, while getting no better at the thing they want, which is making. Nothing in the progress bar reflects the gap. Our member had completed four courses and could not start a file.

Three signs you are in it

You can follow along with a video and the code runs, but when you close the video and reopen the file the next day you cannot explain why you made two of the choices in it. The code was transcribed, not written. This is the earliest and most reliable sign.

The second is that you have started more than two courses in the same language without finishing one. Starting a new course feels like progress because the first hour of any course is easy, and it removes the discomfort of being stuck at hour twelve of the previous one. I have had club members with five half finished Python courses and a strong sense that they were working hard, which they were.

The third sign is the telling one. You have an idea for something you want to build, and your plan for building it is to find a tutorial that builds exactly that. A learner who is out of tutorial hell looks for a tutorial about one piece of the problem. A learner inside it looks for a tutorial about the whole thing.

Why telling people to stop watching tutorials is bad advice

The usual prescription is blunt: stop consuming, start building. I have watched that advice do harm. A beginner who abandons all structured material at hour twenty of learning Python has a blank file, no idea what a reasonable first project looks like, and about ninety minutes of willpower before the whole thing feels like proof they are not cut out for it. We lost two club members that way before I changed how I say it.

Tutorials are a reference format, and reference formats are useful at the moment you have a question. The problem is sequence, not content. Watching a two hour video and then trying to build is backwards. Trying to build, hitting a wall at the point where you need to read a file, and then watching eight minutes on reading files is the same material doing useful work.

So the honest advice is to invert the order rather than quit. Keep the courses, keep the documentation, keep the video channels. Just stop opening them first. In our club we ask mentors to answer every stuck moment with a question before a link, which is slower and keeps people building. The method in breaking a coding problem into small steps is what we hand people instead of another course link.

A first project that fits one week

Scope is where this is won or lost. Almost every failed first project I have seen failed because it was too big, not because the learner was not ready. A good first project after about thirty hours of study has one input, one transformation and one output, and no user accounts, no database and no website.

  1. Pick something from your own week that you currently do by hand. Renaming photo files, adding up a column from a receipt, splitting a long text into lines of a fixed length. Boring is the point.
  2. Write the whole thing in plain sentences first, one line per step, before you open an editor. If you cannot write six sentences, the project is still too vague.
  3. Set a budget of about three hundred lines and four evenings. If the plan clearly needs more, cut a feature rather than extending the deadline.
  4. Build the smallest version that runs end to end on one hardcoded input, even if the output is ugly. Get to a working thing on night one.
  5. Only then make it handle real input, handle a bad input without crashing, and print something readable.
  6. When stuck, spend fifteen minutes on your own, then search for the single specific thing you need, not for the project.
  7. Show it to one other person and ask them to run it on their own machine. That step finds the assumptions you did not know you had made.

The member who sat in front of the blank file wrote a script that renamed about four hundred holiday photos into date order. It was 90 lines, it had one embarrassing bug that renamed two files to the same name, and he fixed it himself. The next thing he built took him two weeks and he never asked me for a tutorial link again. Group settings help here, and the list of coding club projects for mixed skill levels covers ones that work with several people at different stages. More starting points sit in the first steps section.

FAQ

How many hours of course material is enough before building?

Somewhere around twenty to forty for a first language, which usually means variables, conditionals, loops, lists, dictionaries and functions. Past that point extra material has sharply diminishing returns until you have built something, because you have nowhere to attach it.

Is it normal to forget syntax constantly while building?

Completely. Professionals look up string formatting and argument order several times a week. Forgetting syntax is not the same as not knowing how to program, and confusing the two is one reason people retreat into courses.

Should I finish the course I am halfway through first?

Not before you build. Run them side by side: one project, one course, with the project taking priority when time is short. Finishing the course after your first project is also much faster, because the later sections finally have a use.

What if my project idea turns out to be too hard?

Cut it down rather than swapping it. A photo organiser that only handles one folder and one file type still teaches you the same things, and finishing a reduced version builds the habit. Abandoning projects for new ideas is tutorial hell wearing different clothes.

IA
Imogen Achebe

Imogen started a coding club at her school and now trains volunteer mentors. She writes about first steps in coding and projects that work for groups of mixed ability.

More posts by Imogen

More in First Steps

01doorganico 084goad 3hot8 4465456 after5internprogram ahandfulofblessings ahmadpc ahomcybersecurity allodialresources annodex antiquesandperiodcollectibles aotc asianworldkashmir beedlectrics bloggertemplatefree bluefeatheragency bodyweightsolution campaign08blog carfixadvisor catstreetcollective cbstvsports cnfanspurchasing committeeof500yearsofdignityandresistance covertopsdjs cs-kaiyuangame cuestacomunicaciontotal cxoutlet dancebetgame deskgearhub destinyvillastay detectmagazine di33 diamondsteelbuildings donmo dyanadropship emarsysfinance emimattl escapechan eskitarih evautoplay everythingweddings-orlando farmzone feedviewerapp foxstudiosscratch gamevui123 gleasongrade greetingsday hacklabasu haskell iw-kaiyun jagoanproperti jilidskripsi joltbusinessfinance juegodepokergratis juegospucca kaeru-festival latestmehndidesigns lestanzediottaviano litemagazines localcommunityhero lustrsazan mariashebets menswheels newwebstechs1 nikkit ootheday oxigenvpn plurfitness prefetial probudgetcarpetcleaning psychicmrsmartin pyaten qvantor rejoignezlogis rexzbot riselayouts ruchin rwxqsgd5 sakaltime shibiaowang shop-bot skrtips spotlesshaven tetapatrium topselller uneplanteartificielle vipertechcr webtech1223411 wo-kygaming yamaha-mekar yeknava yoybuysheets zenunwa yamaha-mekar jilidskripsi ankertoto ankertoto ankertoto