Honest Take — Before You Begin
Let me address the elephant in the room. You are a Rails engineer looking at React and somewhere in the back of your mind is the question: "Is this replacing me?" No. But ignoring…
React Deep Dive covers: The Road to React, JavaScript Masterclass. Master React from fundamentals through advanced patterns — components, hooks, state management, routing, performance optimization, and testing. Use your Epic React and Testing JavaScript investments. This is the centerpiece of the curriculum.
React components are like Rails partials with state. props are like locals: in render partial: "user", locals: { user: @user }. React's useContext is like Rails' Current attributes — a way to make data available deep in the component tree without passing it through every level. React Router is like routes.rb but running in the browser. useState is like an instance variable that triggers a re-render when it changes. The mental model shift: in Rails, the server renders HTML and sends it; in React, the browser renders the UI and asks the server for data. Understanding both models makes you dangerous.
This course unlocks once you've finished its prerequisite. Open prerequisite →
Let me address the elephant in the room. You are a Rails engineer looking at React and somewhere in the back of your mind is the question: "Is this replacing me?" No. But ignoring…
You have shipped interactive features for years without React: a Stimulus controller here, a Turbo Frame there, and the page updates without a full reload. So here's the honest qu…
Here's an experiment: open any React codebase and delete the JSX from your mind. What's left? Functions that take arguments and return values. Functions passed to other functions.…
Work through each item before the checkpoint.
A full React application (Vite + TypeScript) against an API contract — auth, routing, loading/error states, optimistic updates. The tests run against a mocked API (msw) so CI grad…
5 lessons. Read in order; spiral back when you need to. By the end you'll have used the core ideas twice — once on the abstract, once on something you'll meet at work next week.