Why your brain learns faster by doing than by studying, and the neuroscience that explains it
I spent months on Codewars. One to two problems a day, every day. When I couldn't figure out the answer I would look it up and memorize it.
I also bought courses. Multiple. I knew the basics of JavaScript well enough to talk about it.
And yet nothing really stuck. The Codewars questions felt abstract and disconnected. The examples made no logical sense to me. I would finish a problem and think okay, and? My brain would not hold onto it because it had nowhere to put it.
Then I got a job that threw me into real code. Real systems. Real consequences.
And everything changed.
The moment it clicked
I remember the specific moment I knew something had shifted.
I got a ticket that required updating a complex, long script. Hundreds of lines of code. The kind of thing that would have made past me close the laptop and go make a coffee and quietly panic.
Instead I sat with it. Read through it. Understood what it was doing, where to go in, what to change.
I did not memorize my way to that moment. I built my way there through months of real work with real purpose.
That is not a coincidence. That is neuroscience.
What is actually happening in your brain
When you learn something in a real context your brain does something different than when you study it abstractly. It does not just store the information, it stores it connected to everything around it. The system it lives in, the problem it solves, the feeling of figuring it out.
This is called contextual learning. Your hippocampus, which handles memory formation, encodes information much more effectively when it is attached to a meaningful experience. Abstract exercises give it nowhere to anchor. Real problems give it a whole ecosystem to hold onto.
There is also the dopamine loop to consider. Every time you fix something real like a bug, a broken integration, a script that finally runs correctly your brain releases dopamine. That dopamine hit reinforces the behavior and the learning attached to it. Your brain literally marks that moment as worth remembering.
Why algorithms and abstract exercises are so hard for certain brains
Here is the thing nobody says out loud. Codewars and algorithm challenges are not bad. They work for some people. Specifically they work for people who can hold abstract problems in their head and find satisfaction in solving them without real world context.
Not everyone's brain works that way.
Some people, and I am clearly one of the, need the concrete thing first. The real system, the actual purpose, the tangible result. The theory makes sense after the experience, not before it.
Neuroscientists call this bottom up learning. You build understanding from specific real experiences upward toward general principles. The opposite, top down learning, starts with the abstract concept and works toward application. Neither is better. They are just different and most technical education assumes everyone is top down.
If you have ever felt stupid because you could not get through algorithm challenges, you are probably not stupid. You are just bottom up in a top down world.
What actually worked for me
Real projects with real stakes. A job that required JavaScript every single day for eight hours. Tickets with consequences. Systems I could break and fix and break again.
The repetition mattered too. Doing the same types of problems over and over in slightly different contexts until the patterns stopped being something I had to think about and became something I just saw.
That is how procedural memory forms. The same way you learn to drive or surf. Not by studying the theory but by doing it until your brain stops treating it as a conscious effort.
How to use this if you are learning right now
Stop grinding abstract exercises if they are making you feel like you are not smart enough. That feeling is your brain telling you it needs context not confirmation that you are broken.
Find a real project. Build something you actually care about even if it is small and messy. Contribute to open source. Get a job that throws you in the deep end. Find any context that gives the code a reason to exist and your brain something real to hold onto.
The courses are not useless. The foundation matters. But the foundation only becomes a building when you have something real to build.