Six months ago, I sat down with a YouTube playlist, a blank notebook, and one goal: learn Python. What I did not expect was how hard it would be, not the Python itself, but figuring out how to actually learn it.
I started with a YouTube playlist. Simple enough. Except nobody tells you what to do after you watch a video. Do you rewatch it? Take notes? Jump straight to code? I had no system. I'd watch a concept, feel like I understood it, open VS Code, and stare at a blank file.
That's when I realized I had fallen into passive learning. And passive learning in the age of AI is a particularly dangerous trap, because it's so easy to confuse activity with progress. I could watch a video, feel good. I could ask Claude to explain a concept, feel good. I could even ask AI to write code, read it, nod along, and feel like I'd learned something. I hadn't. I'd just consumed. There's a difference.
The real moment of honesty came when I was stuck on a coding problem. My instinct, everyone's instinct now is to open ChatGPT or Claude immediately. And I knew, sitting there with the cursor blinking, that if I did that every single time I got stuck, I was building nothing. My brain would never develop the muscle of working through problems. I would be someone who can prompt AI to code, not someone who can think in code. And in a world where AI can already write decent code, the person who can't think independently isn't valuable. They're replaceable.
So I had to build a system that forced me to actually learn. After a lot of trial and failure, I landed on a 5-phase checklist that I wrote out by hand and kept next to my laptop.
Phase 1: is what I call First Contact — watch one focused video, then write a summary purely from memory, then discuss it with an LLM not to get answers but to pressure-test what I thought I understood.
Phase 2: is Deep Understanding — read a written source, write proper notes, map the concept visually, and list every edge case and exception I can find.
Phase 3: is Hands-On Practice — write 3 to 5 small isolated examples from scratch, then intentionally break the code, because understanding why something breaks teaches you more than getting it right.
Phase 4: is the Stress Test — ask an LLM to quiz me until I break, teach the concept back to it, and ask "what would an interviewer ask about this?"
Phase 5: is Cement and Connect — use the concept in an active project, write one thing I'd tell a fellow learner about it, and schedule a spaced review.
The rule I set for myself throughout all of this: AI is a tool for testing and pressure, not a crutch for getting unstuck. When I'm stuck on a problem, I sit with it. I struggle. I come back. Only after genuine effort do I use AI — and even then, I ask it to guide me, not solve it for me. It wasn't comfortable. It still isn't. But six months in, I'm now working through Python libraries and starting ML theory, and for the first time it feels like a foundation, not a facade.
If you're somewhere in the early weeks of learning to code, the question isn't which resources to use. It's whether you're actually building something in your brain, or just moving content through your eyes. The difference matters more now than it ever did before.
Top comments (0)