Timeline & Suggested Order
How long does this take, and in what order should you actually do it? Honest version.
Timeline & Suggested Order
The suggested order
This schedule complements the sidebar concept track (Chapters 1–17 in order). The two tracks overlap — that's intentional. Use them as overlapping tracks:
- Always-on track — Part IV (Meta-skills). Read How to actually learn and Tutorial trap before you start Stage 1. They change how everything after them sticks.
- Primary track — Part I, in order. Stages 0 → 12, no skipping. This is 4–9 months.
- Lookup track — the rest of this guide. When Stage n points at Foundations or Tech Stack, follow the link, read the page, return.
- Once you're shipping — Part II. As you complete Stage 11+, start sampling the trends and Tier 1 picks against your own projects.
- Once you're mid-level — Part III. Roughly 1–2 years in, when "does this code work" stops being the hard question.
How long does all this take? — honest version
Marketing copy on bootcamps says "6 months to job-ready." Most bootcamps' actual placement rate at 6 months is much lower than that, and the people who do place often have a strong pre-bootcamp foundation (CS adjacency, a prior career in a logic-heavy field, etc.).
The honest range:
| Background | To Stage 9 (first portfolio) | To Stage 12 (job-ready) |
|---|---|---|
| Total beginner, part-time (10 hrs/week) | 6–9 months | 12–18 months |
| Total beginner, full-time (35+ hrs/week) | 2–4 months | 5–9 months |
| CS-adjacent (already programs in another language) | 1–3 months | 3–6 months |
| Working dev refreshing | days–weeks | not the target — go to Part II |
These are honest numbers — not the inflated ones bootcamps advertise. Plan for the upper end. If you hit the lower end, great.
How many hours per week, sustained. 10 hours every week for 9 months beats 40 hours for one month followed by burnout, every time. The dropouts in coding-as-a-second-career are almost always burnout-driven, not talent-driven.
A note on prerequisites
This roadmap assumes you can read English at a high-school level and use a computer comfortably. It does not assume:
- Math beyond arithmetic (you'll meet a little algebra and Big-O later; both are learnable on demand)
- Any prior programming experience
- A CS degree (helpful but absolutely not required)
- A "STEM brain" (a meaningless concept)
If you're worried about whether you can do this: you can. The variable that matters is sustained hours, not innate aptitude.