3. Roadmap — Overview
The complete learning path. From zero, through the 2026 stack, into the fundamentals every framework cycle leaves untouched, ending with the meta-skills that let you keep learning.
Chapter 3: The Roadmap
From zero to production engineer — the ordered curriculum that pairs with this guide.
The rest of the book is organized by topic — how the web works, the stack, workflows by team size, decisions, AI, career. This chapter is organized by progression. It tells you what to learn, in what order, with the why at each step and a concrete project to cement it.
The two views overlap deliberately. When a stage says "learn React fundamentals," it links into the Frontend Frameworks page for depth. When the Modern Stack section says "adopt Drizzle + Zod," it links into the ORMs page for context. The roadmap is the path; the rest of the guide is the terrain.
Becoming a good web developer isn't one skill — it's roughly twelve overlapping skills, and the order matters. Most beginners thrash because they try to learn React before they've written 100 lines of JavaScript, or copy Tailwind classes without understanding the box model underneath, or build a Next.js app before they've ever deployed a single HTML file. The order here is the order that actually compounds.
The four parts
| Part | What it covers | For whom |
|---|---|---|
| I. From Zero | 13 stages, ~4–9 months part-time, takes you from "never written code" to "shipped full-stack" | Complete beginners |
| II. Modern Stack | The 2026 stack: 6 trends + Tier 1/2/3 picks (adopt, know, skip) | Working devs choosing tools |
| III. Beyond the Stack | CS fundamentals, engineering judgment, systems thinking, security | Mid-level devs leveling up |
| IV. Meta-skills | How to actually learn, AI as a learner, asking questions, the tutorial trap | Anyone stuck |
Where to enter
- Never written code? → Part I, Stage 0. Don't skip.
- Can write JavaScript, shipped a small project? → Part II. Use Part I's later stages as a self-check.
- Working dev who knows the modern stack? → Part III. The fundamentals that don't change with framework cycles.
- Stuck or losing momentum? → Part IV. Being stuck is part of the process; having strategies for it is the skill.
How the roadmap pairs with the rest of the guide
The chapters that follow this one (Lifecycle, Tech Stack, Workflows, Decisions, AI, Career) are reference material. You don't read them straight through — you reach for them when a roadmap stage points you at them.
For example, Stage 6 — React fundamentals links into:
- Tech Stack: Frontend Frameworks — for the comparative why
- Foundations: SPA / MPA / Hybrid — for the underlying model
- Decisions: Boring vs Shiny — for when to even reach for React in the first place