Course
React Engineering
React the way production teams use it — hooks discipline, state architecture, data fetching, performance, and the component patterns that survive contact with real requirements.
Core Model
Rendering, state, and effects — the mental model everything else builds on.
- 01Thinking in React: The Render ModelWhy React re-renders, what 'UI as a function of state' actually buys you, and how to predict what a component does before you run it.20mOpen
- 02Hooks Discipline: useState, useEffect, and the Rules That MatterThe rules of hooks aren't arbitrary — they exist because hooks are just an array of slots. Plus the useEffect habits that prevent 90% of effect bugs.22mOpen
- 03Component Design: Composition, Lifting, and Escape HatchesWhere state should live, why props drilling is a design smell, and the three composition patterns that cover almost every UI.20mOpen
Real Applications
Data fetching, forms, and state architecture at app scale.
- 01Data Fetching Without the FlickerLoading, error, and empty states are part of the feature. Fetch patterns that handle races, stale data, and cancellation properly.22mOpen
- 02Forms and Validation That Don't Fight the UserControlled vs uncontrolled inputs, schema validation, accessible errors, and the submission states most forms get wrong.20mOpen
- 03State Architecture: Local, Shared, Server, URLWhere each kind of state belongs — and why most 'we need Redux' moments are actually 'we haven't decided what kind of state this is.'20mOpen
Shipping Quality
Performance, accessibility, and code organization.
- 01React Performance: Measure, Memoize, DeferThe real perf playbook — find what's actually slow before optimizing, and the three tools (memo, transitions, code splitting) that fix 95% of it.22mOpen
- 02Accessible Components by DefaultSemantic HTML does the work — when you must build custom widgets, follow the ARIA pattern and keep keyboard+screen-reader paths real.18mOpen
- 03Organizing a React CodebaseFeature folders over type folders, colocating related code, and the boundaries that keep a growing app navigable.18mOpen