React JS · Learning Paths
Self-Taught vs Bootcamp: Learning React JS Faster
React is one of the best-documented front-end libraries. The official site, react.dev, was rewritten in 2023 around function components and hooks, with interactive examples and exercises. That makes React a good candidate for self-study. Whether you will actually get faster results alone depends on one thing more than any other: how well you already know JavaScript.
Check your starting point
Before React, you should be able to write, without looking up each line: functions and arrow functions, array methods (map, filter, reduce), destructuring and spread, modules (import/export), and fetch with async/await. If those are shaky, spend two to four weeks on them first. Most React confusion is actually JavaScript confusion. HTML, CSS and JavaScript first steps covers the groundwork.
A self-taught plan with milestones
Each milestone ends with something you can show. If you hit them roughly on schedule, self-study is working.
- Weeks 1–2: components and state. Work through react.dev's "Learn" section: JSX, props,
useState, rendering lists, handling events. Milestone: a to-do app with add, delete and filter. This to-do list walkthrough is a reference if you get stuck. - Weeks 3–4: effects and data.
useEffect, fetching from an API, loading and error states. Milestone: a page that searches a public API and shows results. You should be able to write and explain a small custom hook like this one:If you can say why theimport { useEffect, useState } from "react"; export function useFetch(url) { const [data, setData] = useState(null); const [error, setError] = useState(null); useEffect(() => { let ignore = false; setData(null); setError(null); fetch(url) .then(res => { if (!res.ok) throw new Error(`HTTP ${res.status}`); return res.json(); }) .then(json => { if (!ignore) setData(json); }) .catch(err => { if (!ignore) setError(err.message); }); return () => { ignore = true; }; }, [url]); return { data, error, loading: !data && !error }; }ignoreflag is there (a slow, outdated request must not overwrite newer results), you understand effects better than many beginners. - Weeks 5–6: structure. Routing with React Router, forms with validation, lifting state up, context for shared data. Milestone: a multi-page app with a form.
- Weeks 7–8: real-project habits. TypeScript basics, component testing with Vitest or Jest and React Testing Library, Git with meaningful commits. Milestone: the same app, typed and with tests.
- Weeks 9–10: ship it. Deploy, write a README, and ask two developers to review the code. Milestone: a live portfolio project, such as one of the ideas in building a portfolio site with React and Node.
The timings assume roughly 10–15 hours a week with JavaScript already in place. Slower is fine; stopping is the real risk.
What a bootcamp adds
| Need | Self-taught | Bootcamp |
|---|---|---|
| Learning material | Official docs and free tutorials; very good | Curated sequence; quality varies by provider |
| Code review | Only if you seek it from communities or friends | Usually included; ask how often and by whom |
| Deadlines and pace | Self-imposed | Built in |
| Team experience | Hard to get alone | Group projects with pull requests, in good programmes |
| Cost | Time only | Course fee |
| Career support | Your own effort | Varies; ask for specifics |
Signs you would benefit from structure
- You have restarted a React tutorial more than twice.
- Weeks pass without a finished milestone.
- Your code works but you cannot explain why, and nobody is reviewing it.
- You learn better with a fixed timetable and other people around you.
If two or more apply, a structured course may get you there sooner. When comparing options, ask to see a past student's project repository, check how much time goes to code review, and make sure the syllabus covers testing and deployment, not only components.
Either way, measure the same thing
Employers judge React candidates on what they have built and how they talk about it. Prepare for questions like those in React hooks to know before interviews, and make sure at least one project shows routing, forms, API data, tests and deployment. If you are still choosing a front-end library, React or Angular first may help.