I spent a whole month "learning to code" without writing a single program that was mine.
I watched tutorials at 1.5x speed in my hostel room after classes, nodded along, understood everything the instructor did — and then, facing a blank editor, could not start.
This post is about the one small rule that pulled me out, the day it broke completely, and the patch I added so it would not break that way again.
First, what tutorial hell actually felt like
It did not feel like laziness. That is the sneaky part.
It felt like studying. I had notes. I had a playlist progressing nicely — 34 videos watched, a number I was weirdly proud of. If you had asked me to explain how a loop worked, I could have explained it well. I had simply never survived the ten ugly minutes between "I understand" and "it runs," because the tutorial always carried me across them.
Understanding someone else's code while they narrate it is a real skill. It is just not the skill of writing code, the same way watching a man swim is not swimming, however attentively you watch 🏊
The rule (all 3 steps of it)
The rule I landed on is small enough to survive a tired weekday, which most systems are not.
Step 1 — When you get stuck, set a timer for 20 minutes and struggle on purpose. Read the error message word by word. Change one thing at a time. Print the values. Talk to the screen. No searching, no asking, no "quick peek" at a video. Twenty minutes of honest attempts.
Step 2 — When the timer ends, write the exact question in one sentence. Not "my code doesn't work." A real question: "Why does my total come out double every second item in the list?" Written down, in a notebook or a notes app — the writing is not optional, and the reason is coming.
Step 3 — Only then, search or ask — using the sentence you wrote. Paste the sentence into the search bar. Or send it to the group chat. The sentence is the search. If you cannot write the sentence yet, you are not stuck on an answer. You are stuck on the question, and another 20 minutes of poking at the code is how you find it.
What changed (quietly, not magically)
My sessions got shorter and strangely more satisfying. A session stopped being "watch three videos" and became "get stuck twice, properly."
My questions in the class group chat changed, and so did the answers. "Sir, code not working, help" gets sympathy. One precise sentence gets a precise reply, usually within minutes, because people can actually help a question that fits in their head.
And I stopped rewatching entire tutorials to find one lost minute. Most of what I needed was behind my own written sentence, on a forum, answered years ago for someone with the same sentence.
The day it failed: 3 hours, one bug
Then came the evening the rule met a stubborn bug and lost.
I was extending my little grade program — adding a class average — and the average kept coming out wrong. Not wildly wrong. Suspiciously, plausibly wrong, the worst kind.
The timer went off at 20 minutes. And I said the four most dangerous words in learning: "just one more try." I said it again at 40 minutes. I said it at an hour. Stopping felt exactly like quitting — like the bug was winning and the rule was an excuse — so I kept going until 3 hours had gone and I was changing random lines out of spite, understanding less at midnight than I had at nine.
The next morning, rested, I found it in about four minutes: I was adding each new mark to the total and re-adding the previous total inside the loop. Classic. A rested brain saw it instantly. A tired brain had protected the bug for three hours like it was a pet.
What the rule got wrong (the catch)
The rule assumed I would obey the timer. It forgot that at minute 20, I am not a rational person following a system. I am a person in an argument with a machine, and the machine is winning.
But notice what I skipped that night: Step 2. I never wrote the question down. In my head, the question stayed as a fog — "the average is wrong somehow" — and fog cannot be searched, cannot be sent to a friend, and cannot be argued with. The bug survived because the question never became a sentence.
So the patch is about making Step 2 unavoidable, and it is embarrassingly physical: when the timer ends, I stand up, get water, and write the sentence before I am allowed to sit back down. Half the time, the sentence solves it while I am writing it — the act of naming the wrongness points at the line. The other half, I hold a question so specific that searching it takes two minutes.
The rule is no longer "try hard for 20 minutes." It is: you may not be stuck in your head. Be stuck on paper, where people can help you.
The 7-day challenge (try it with me)
Do not take my word for any of this. Take it for one week:
- Code something small every day, or most days.
- Every time you get stuck: 20 minutes alone, then one written sentence, then search or ask.
- Count your days honestly, including the ones where the timer beat you.
Then come back and report. I want three things from you: your score out of 7, the hardest question you had to write down, and whether writing it solved anything before the search did.
I'll be in the comments with my own score. It will not be 7.
