Most roadmaps show you a map of everything and let you drown in it. This one is opinionated. It tells you what to pick, what order to learn it in, and — the part nobody marks — exactly where the job-ready line sits.
This isn't my opinion, it's what the major curricula actually say. roadmap.sh's backend track states it plainly: "Learn one language and build lots of projects before moving on." The Odin Project is blunter: "The important thing is to not switch halfway through; this will only set you back."
The people still stuck after two years usually didn't pick wrong. They kept starting over.
No credible source claims one is objectively the better first language. What actually decides it:
JavaScript if you want to build for the web. You'll have to learn it eventually anyway — it's the only language browsers run. Python if you want AI, data, or automation. It's also the prerequisite language of the whole AI-engineering world.
Anthropic ran a randomised controlled trial with 52 mostly-junior engineers learning an unfamiliar Python library. The group using an AI assistant scored 50% on the comprehension quiz. The group coding by hand scored 67% — close to two letter grades. The biggest gap was in debugging. And they were only ~2 minutes faster, which wasn't statistically significant.
The people who did well used AI to explain things, not to produce things. So: try it yourself first, get stuck, then ask AI why. Don't skip the getting-stuck part — that's where the learning actually happens.
You want to build things people can see and click. Fastest visual feedback.
You want to build the systems behind the app. Data, APIs, servers.
Both. Longer, but you can build an entire product alone.
Building products on top of AI models. Not a beginner path — read the warning.
Note the name: Frontend Web. This path is about browsers. Mobile and desktop are different roads.
With solid HTML/CSS/JS, one framework, TypeScript, Git and deployed projects, you can apply. Everything below makes you better, not employable-er.
The systems behind the screen. Data, logic, APIs.
roadmap.sh marks it right after APIs — before Docker, Kubernetes, microservices and message queues. Most beginners believe they need the whole map first. They don't.
Frontend plus backend. This is the only path with checkpoints baked into the official roadmap, and they're worth following literally.
You can build and ship a whole product by yourself. That's the bar.
The official roadmap says 3 months is realistic only if you already know one half and are filling in the other. From zero, it isn't.
The official roadmap lists a hard prerequisite: frontend, backend, or full-stack first. AI engineering is a specialisation you add on top of being a developer, not a shortcut around becoming one.
Also worth separating: an AI Engineer builds products using existing models. An ML Engineer builds and trains the models — that's the path with the linear algebra and statistics. This isn't that.
Every "become a developer in 6 months" claim I could find traced back to a company selling a course. None published a methodology. So here are only the numbers that come from the free curricula themselves — divide by your own hours per week.
| Source | What they state |
|---|---|
| freeCodeCamp | ~300 hours per checkpoint certification; ~1,800 hours for the full Certified Full Stack Developer capstone |
| Full Stack Open | 15–20 hours per part, 14 parts. Requires 100–200 hours of prior programming experience first |
| Teach Yourself CS | 100–200 hours per subject, 9 subjects |
| roadmap.sh (full-stack) | 3 months — but only if you already know one half |
Stop counting months. The backend roadmap marks "you know enough to get a job" immediately after learning APIs — long before the scary infrastructure topics. Scope beats time as a measure of progress.
1. Pick one path. Finish it. Switching is the single most common way people lose two years.
2. Build ugly things. A finished ugly project teaches more than a beautiful tutorial you followed along with.
3. Learn the language before the framework. React on top of shaky JavaScript collapses the moment something breaks.
4. Get stuck on purpose. Try it yourself, fail, then ask AI to explain. The struggle is the mechanism, not an obstacle to it.
5. Ship publicly from day one. Push to GitHub, deploy it, post about it. Proof compounds; private work doesn't.
6. You need far less than you think to get hired. The job-ready line is much earlier on every one of these maps than beginners assume.