It probably started with a Google search.
"Best free coding course for beginners."
Or maybe it was a YouTube video. Or a Reddit thread. Or a Twitter reply from someone who learned to code in six months and got hired at a fintech.
Wherever it started, within 48 hours I had accounts on:
freeCodeCamp ✓
The Odin Project ✓
Udemy ✓
Udacity ✓
Coursera ✓
And I hadn't written a single line of code yet.
The First Week on Every Platform
freeCodeCamp felt good. Structured. Little boxes to fill. Instant feedback. I flew through the first HTML lessons and felt like a genius.
Then someone on Reddit said freeCodeCamp wasn't good enough for getting a job. That you needed projects. That the certificates meant nothing.
So I opened The Odin Project.
TOP felt serious. Real. Like actual developers built it for actual developers. I loved the philosophy. But it was harder. Less hand-holding. I got stuck on the first JavaScript exercise and spent two hours going nowhere.
So I opened Udemy.
Udemy had a course with 47,000 ratings and a thumbnail of a guy pointing at code. It was on sale for ₦3,000 down from ₦85,000. Obviously I bought it. Obviously I never finished it.
Meanwhile someone told me Udacity had nanodegrees. Nanodegrees sounded official. Like something you could frame. I signed up for the free trial.
You see the pattern.
What I Told Myself Each Time
Every switch came with a justification. A completely reasonable, totally logical reason why this platform wasn't working and that one would be better.
"freeCodeCamp is too shallow. I need real projects."
"The Odin Project is too hard with no guidance. I need structure."
"Udemy moves too slow. I'm wasting time."
"Udacity is too expensive. I can't focus knowing I'm burning money."
Every excuse was technically true. Every platform has real weaknesses. That's what made the trap so effective — it was disguised as rational decision-making.
But here's what was actually happening:
I was using research as a substitute for learning.
Every hour I spent comparing platforms was an hour I wasn't spending writing code. Every new account I created felt like progress. It had the shape of productivity without any of the substance.
I was the person who buys running shoes, downloads a fitness app, researches the best jogging routes, reads about optimal running form — and never goes for a run.
The Graveyard
Let me show you what two years of platform-hopping actually produced:
freeCodeCamp: Completed Responsive Web Design certification. Cannot remember how to use CSS Grid without Googling it.
The Odin Project: Got to JavaScript Foundations. Stopped at the Calculator project. Told myself I'd come back.
Udemy — The Web Developer Bootcamp: 34% complete. Watched videos at 1.5x speed and felt efficient.
Udemy — JavaScript: The Complete Guide: 12% complete. Bought during a sale. Opened twice.
Udacity: Created account. Did the orientation. Never opened a lesson.
Coursera — Google IT Support: Finished it. It had nothing to do with software development. I just needed to finish something.
YouTube tutorials: Uncountable. Followed along. Closed the tab. Remembered nothing.
This is my graveyard. A collection of half-dug holes.
And here's the painful truth about half-dug holes — they're useless. A hole is only useful when it's deep enough. Depth requires staying in one place long enough to get there.
I kept moving before I ever got deep.
The Question That Broke The Loop
I was in a developer community online — Nigerian devs, people grinding through similar journeys — and someone asked me what I was working on.
I started listing platforms.
"I'm doing a bit of TOP, and I've been going through some Udemy stuff, and I'm thinking of picking up the CS50 course because—"
He stopped me.
"What have you built?"
Silence.
Not silence because I was thinking. Silence because the answer was nothing. Two years into learning to code and my GitHub had a cloned tutorial repo and a HTML page that said "Hello World."
That question broke something open in me.
Because I had been so focused on where I was learning that I had completely forgotten what learning was supposed to produce.
Learning to code produces code. Shipped code. Real projects. Things that work.
I had none of that. Just subscriptions and bookmarks and half-watched videos.
The Decision
I made a decision that felt terrifying at the time.
I closed every tab. Cancelled the subscriptions I could cancel. And I went back to The Odin Project — not because it's the best platform in the world, but because I needed to pick one and it was the one I respected most.
Then I made one rule:
I will not open another learning platform until I finish this one.
Not "I'll try to stay focused." Not "I'll see how it goes." A hard rule. One platform. Full stop.
And then I did something I had never done before in two years of "learning to code."
I started a project and I finished it.
What Finishing Actually Feels Like
The first project I completed on TOP after committing was the Calculator.
The same Calculator project I had abandoned before when I jumped to Udemy.
It took me four days. It was frustrating. I Googled things. I got stuck. I slept on problems. I woke up and tried again.
And when it worked — when I pressed buttons and numbers appeared and the math was right — I felt something I hadn't felt in two years of course-hopping.
I felt like a developer.
Not because the Calculator is impressive. It isn't. But because I had built something with my own hands, with my own logic, that worked. That feeling is not available on any platform. You can only get it by finishing something.
After that I kept going.
Linked Lists. HashMaps. Binary Search Trees. Knight's Travails. A full Battleship game with 22 passing tests written in TDD.
All on one platform. All finished. All mine.
The Truth About "Which Platform Is Best"
I'm going to answer the question you probably Googled to find this article.
Which coding platform is best?
The one you finish.
That's it. That's the whole answer.
freeCodeCamp is excellent. The Odin Project is excellent. A good Udemy instructor is excellent. CS50 is one of the greatest educational resources ever made. They are all good enough.
Good enough is not your problem.
Commitment is your problem.
The difference between a developer and someone who's been "learning to code for two years" is not the platform they chose. It is whether they stayed long enough to go deep.
Any platform taken seriously and completed will produce a developer. No platform hopped between will produce anything except browser history.
What Platform-Hopping Really Is
I want to name what's actually happening psychologically because I think it helped me to understand it.
Platform-hopping is anxiety wearing the costume of optimization.
When you're on a platform and it gets hard — and it will get hard, always, on every platform — your brain looks for an exit that doesn't feel like quitting. Switching platforms feels like a smart strategic decision. It feels like you're being efficient. Cutting losses. Finding a better path.
But you're not. You're running from the hard part.
And here's the brutal irony — the hard part on every platform is roughly the same hard part. JavaScript is hard on TOP. JavaScript is hard on freeCodeCamp. JavaScript is hard on Udemy. The language doesn't get easier because the platform changes.
You cannot outrun the difficulty. You can only go through it.
Signs You're In The Trap Right Now
You might be platform-hopping if:
You have more course accounts than finished projects
You know the pros and cons of six platforms but can't explain how a for loop works
You've restarted "from scratch" more than twice
Your GitHub is empty but your Udemy library is full
You're reading this article instead of doing your current lesson
No judgment. I was every single one of these.
How To Escape
Step one: Pick one platform. Any good one. TOP, freeCodeCamp, a solid Udemy course. It genuinely doesn't matter as much as you think.
Step two: Make a rule. No switching until you finish or until you have a specific, legitimate reason that isn't "this is getting hard."
Step three: Measure progress in projects shipped, not lessons watched. A lesson watched is an input. A project finished is an output. Outputs are what make you a developer.
Step four: When it gets hard — and it will — recognize that feeling as the signal that you're in the right place. Difficulty means depth. Depth means learning.
Step five: Finish something. Anything. Then finish the next thing. Build the habit of completion and everything else follows.
Where I Am Now
I'm still on The Odin Project.
I'm in the Advanced HTML and CSS module, moving toward React. My GitHub has real projects I can explain and defend. I have a Battleship game with 22 tests. I have data structure implementations I built from scratch.
None of that existed when I was hopping between platforms.
All of it exists because I stopped moving and started digging.
The depth was always available to me. I just had to stay in one place long enough to reach it.
One Last Thing
If you're sitting right now with five tabs open — TOP in one, freeCodeCamp in another, a Udemy cart in a third — I want you to do one thing.
Close four of them.
Pick the one that remains. Open your code editor. Start the next lesson.
Not tomorrow. Right now.
The best platform in the world is the one you're actually using.
Kingsley is a CS student at NOUN, Lagos Nigeria, going deep on one path through The Odin Project. Follow my journey on GitHub at github.com/
legacy-king