I spent the first two years of my programming career watching tutorials. Hundreds of hours of them. And I could not tell you what half of those videos covered, because I never did anything with the information besides nod along.
That’s the trap most self-taught developers fall into. You open a 40-minute video on React hooks, follow along, maybe type out the examples. It feels productive. Then a week later someone asks you about useEffect cleanup functions and your mind goes blank.
It’s not an effort problem. Watching and reading are just passive, and passive input has terrible retention. A 2008 study published in Science by Karpicke and Roediger found that students who tested themselves on material retained significantly more than students who simply re-read it, even when the re-readers spent more total time studying. The students who just re-read their notes didn’t even realize they were falling behind. They felt like they knew the material fine.
This is called the testing effect. Once I understood it, I stopped trying to consume more content and started looking for ways to check whether I’d actually absorbed anything.
These are the tools that stuck for me.
1. Obsidian for connected notes
Most note apps are just text files with extra steps. Obsidian is different because it lets you link notes together. Your notes on JavaScript closures can reference your notes on scope and execution context, and over time you get a web of connected ideas rather than a pile of disconnected documents.
I use it for all my technical notes. Every time I learn something, I write a short note in my own words and link it to related concepts. Writing it out forces me to process the information, which is already better than highlighting someone else’s text. And the linking means I revisit older notes without really trying, which turns into accidental spaced repetition.
Free for personal use. Plugin ecosystem is huge. If you learn by writing things down, start here.
2. Anki for memorizing syntax and concepts
Anki has been around forever and it still works better than most flashcard apps because the spaced repetition algorithm is genuinely good. It shows you cards right before you are likely to forget them, which is the whole point of spaced repetition research going back decades.
I use it for things worth memorizing cold: SQL joins, Git commands, HTTP status codes, keyboard shortcuts. The kind of stuff where instant recall saves you 30 seconds of Googling every time, and those seconds add up over months.
Fair warning: making good Anki cards takes effort. Bad cards (ones that are too vague or test recognition instead of recall) waste your time. I keep mine short, one concept per card, and phrase them as questions rather than fill-in-the-blank.
3. A quiz generator for testing yourself on documentation
Reading documentation is necessary but it’s one of the worst ways to retain anything. You scan through, understand it in the moment, and forget the details by tomorrow.
What works better is reading the docs and immediately testing yourself on what you just read. Quizgecko is worth bookmarking for this. You paste in a section of documentation or your own study notes and it generates multiple choice and short answer questions from the content. No setup, no account required to try it. I started using it when I was working through the PostgreSQL docs for a migration project, and it caught gaps in my understanding that I would have missed otherwise.
The research backs this up. A systematic review published in 2024 found that active recall strategies were consistently associated with better academic performance and higher self-efficacy. Quizzing yourself is not just more effective than re-reading; it also makes you more confident in what you actually know versus what you think you know.
4. DevDocs for fast offline reference
This one is less about learning and more about not losing momentum. DevDocs.io pulls documentation for almost every language and framework into one searchable interface, and it works offline.
I keep it in a pinned tab. When I need to check an API signature or whether a method mutates in place, I get the answer in seconds without switching context. Small thing, but staying in the zone for an extra ten minutes adds up fast.
5. Notion for structured learning plans
Obsidian is where I keep notes. Notion is where I plan what to learn. I have a database with every technical topic I’m working through, columns for status and priority, and linked pages for my notes on each one.
Most developers’ learning is reactive. You learn whatever comes up at work or whatever the algorithm shows you. Having even a rough plan changes that. You notice gaps and fill them on purpose. Notion works well here because the structure is completely up to you.
6. Pomofocus for time-boxed study sessions
Pomofocus.io is a simple Pomodoro timer in the browser. 25 minutes on, 5 minutes off. Nothing fancy.
I bring it up because the biggest obstacle to learning is rarely the wrong tool or the wrong resource. It’s sitting down to study, getting distracted after 8 minutes, and never going deep enough for anything to stick. A timer externalizes the commitment. You’re not deciding whether to keep going, you’re just finishing the block. I’ve found that two focused 25-minute blocks of active study do more for me than an hour of half-distracted reading.
7. YouTube and Frontend Masters for initial exposure
I still watch tutorials. I just treat them differently now. They’re for exposure, not retention. I watch a video to get the rough shape of a concept, then go learn it properly by building something or quizzing myself on it.
Frontend Masters is worth the money if you’re learning web dev seriously. The courses feel more like workshops than lectures. But even free YouTube works fine for the initial exposure. The mistake is thinking that exposure is the same as learning.
8. AI coding assistants for active problem solving
Tools like GitHub Copilot or Claude are useful for learning when you use them as collaborators rather than answer machines. Instead of asking “write me a function that does X,” try writing it yourself first, then ask the AI to review it and explain what you got wrong.
That flips the dynamic. You’re retrieving knowledge by writing code from memory, then getting real feedback on where your mental model was wrong. It’s harder than just asking for the answer, but you actually remember things afterwards.
Building a routine that works
None of these tools matter much in isolation. The thing that actually works is the loop: consume something, process it in your own words, then test yourself on it. Read the docs, write a note in Obsidian, generate a quiz with Quizgecko, review your Anki cards before bed. I’ve gotten more out of that routine in six months than I did in years of passive tutorial watching.
The research on this is pretty clear. Spacing your practice out over days and weeks, rather than cramming everything into one session, produces better long-term retention. And testing yourself, even when it feels harder than re-reading, is what actually moves knowledge into long-term memory.
I genuinely believe that thirty minutes a day with active recall built in beats weekend study marathons every time. You don’t burn out, you actually remember things on Monday, and the compounding effect is real. Pick two or three of these tools, use them for a month, and see what happens.
Leave a Comment