Can you build the thing you just watched a tutorial about?
I counted, because I didn't believe myself either: in one month I watched 40 hours of Python tutorials. Full courses. Playlists with checkmarks next to every video.
Here's what those 40 hours actually produced, and what happened when I banned tutorials for a week.
Wait, 40 hours and nothing to show?
Nothing. Not "nothing great." Literally no finished program I could open and run.
I could nod along with anything. Loops? Sure. Functions? Obviously. I had the strange skill of understanding code while someone else typed it, and losing all of it the moment a blank file opened in front of me.
The tutorials weren't bad. That's the uncomfortable part. I was just using them as a warm blanket. Watching felt like studying, and studying felt like progress, and neither one asked me to be stuck.
Where the 40 hours actually went
Since I was counting anyway, I broke the month down, and the breakdown is its own little embarrassment.
About 17 hours was one full beginner course, start to finish, the kind with a progress bar that fills up and makes you feel employed already. Another 11 hours was shorter videos on single topics: dictionaries, file handling, a Tkinter series I never finished because the calculator episode is still sitting at 80% watched. The remaining 12 hours was what I can only call wandering: one video leading to another at 1.5x speed, usually starting from a real question and ending somewhere around "how I would code if I were at Google," narrated by a man whose job I do not have.
Notice the pattern. Almost none of it started from a problem I actually had. It started from a thumbnail. I was eating meals someone else had ordered.
The rules I gave myself (so I couldn't cheat)
For 7 days: no YouTube tutorials, no video courses. Documentation was allowed. Searching error messages was allowed. Reading was allowed.
Building was not optional. Every day, one small thing, finished or not.
What actually happened, day by day
Day 1 was humbling in a way I did not enjoy. I sat down to write a program that renames messy downloaded files, got stuck on how to even list files in a folder, and spent 40 minutes in the documentation. Forty minutes for something a tutorial would have shown me in four.
Day 2 I nearly relapsed. I had the YouTube tab open before I even noticed my hand doing it. Closed it. Felt ridiculous. Finished nothing that day except reading about string methods, slowly, like a man reading a phone book.
Day 3 the file-renamer worked. Twelve files renamed in one go. I ran it three extra times just to watch it happen.
Days 4 and 5 I built an expense splitter for my mess bills. I share a house with other students, we split food costs, and the monthly argument about who owes what is a local tradition I wanted dead. The splitter takes names and amounts and prints who pays whom. Ugly output. Correct numbers.
Days 6 and 7 were mostly fixing the splitter. Edge cases. What if someone paid nothing? What if there are five people, not four? Each fix taught me something a playlist never had, because the bug was mine.
A small scene from day 5, because it's the one I keep telling people about. The splitter printed that Arif owed me 340 taka and I owed Arif 340 taka, at the same time, in the same report. Both numbers were "correct" by the code's logic, which meant my logic had a hole in it. In tutorial-land, this is where the instructor says "and now we fix the bug" and fixes it in one motion, smiling. Alone, I had to sit with it for an hour, tracing amounts on paper like an accountant from 1950. When it finally balanced, I understood my own program for the first time. Not Python in general. Mine. That distinction turns out to be the whole game.
The splitter has since survived two real month-end settlements. Nobody in the house has framed it, but nobody has argued about the food money since either, and in a student mess that is close to a peace treaty.
Total for the week: 2 working programs, roughly 9 hours of actual building. The 40 hours of watching produced zero. Nine hours of struggling produced two, plus a peace treaty.
The honest catch
This was not a clean motivational story, so let me not sell it as one.
Documentation is dry and slow, and I am not going to pretend otherwise. A tutorial gives you the answer in the order you need it. The docs give you everything in the order the library author felt like writing it. Some evenings I spent an hour to learn one small thing, and I can't promise it was an efficient hour.
And day 2 nearly ended the whole experiment before it started. If I'd had a deadline or an exam, I'd have caved and watched the video, and honestly that might have been the right call.
One more thing I got wrong: I assumed the 40 hours were wasted. They weren't, entirely. The vocabulary was in my head. I knew what a function was. The week didn't teach me Python from zero. It taught me that knowing about code and writing code are two different muscles, and I had only ever trained one.
What changed after the week ended
I still watch tutorials. I'm not doing a purity thing here.
But the ratio flipped. Now it's roughly one hour of watching for every three hours of building, and the watching is targeted. I get stuck on something real, I watch the twelve minutes that unstick me, I close the tab.
The blank file doesn't scare me anymore. It just sits there, and I type something wrong, and then something less wrong. That loop, it turns out, was the entire skill.
So now I'm curious about your numbers, because mine embarrassed me into changing:
How many hours of tutorials did you watch this month?
How much of that turned into something you can actually run?
How many tutorial hours have you logged this month?
Top comments (0)