react
React, zero to senior
How React actually renders — reconciliation, state batching, effects, memoization — past tutorial level.
Start track →Render, commit, reconciliation
React is a render-phase pure function plus a commit phase; reconciliation by type+key decides what survives.Effects, memoization, context
Effects synchronize with external systems, memoization trades memory for render time, context re-renders subtrees.Data fetching: effects, Suspense, query libraries
Fetching is a cache problem, not a request problem — races, waterfalls and invalidation decide UX, not the fetch call.Forms, actions, optimistic UI
A form is a state machine: who owns the value, when it validates, and what the UI claims before the server confirms.Performance: measure, then cut
Profile before optimizing: most React slowness is render volume — virtualization, transitions and splitting beat micro-memo.State architecture: colocation to external stores
Place state at the lowest component that needs it; reach for context, reducers or external stores only when colocation breaks.Testing React applications
Test what the user sees, not the implementation: RTL queries by role, user-event for real interaction, msw at the network seam.Concurrent React
Concurrency is interruptibility: Suspense boundaries shape loading, deferred values shed urgency, streaming SSR ships HTML in waves.Error handling and recovery
Error boundaries catch render crashes only: handlers, effects and promises escape them — recovery means reset keys, retries, partial UI.Accessibility in React
Semantics first, ARIA as a contract: focus is state you must manage, composite widgets follow WAI-ARIA patterns, a11y is testable in CI.React Server Components
RSC splits the tree by environment: server components render to a serializable payload, client islands hydrate — props cross a wire.Design systems in React
A design system is an API: composition over configuration, headless logic + styled skins, polymorphic asChild, tokens as the contract.Animations and interaction
Animate transform and opacity on the compositor; FLIP fakes layout animation, View Transitions snapshot the DOM, gestures need budgets.React in production
Production React is operations: version migrations without rewrites, RUM wired to releases, profiling real users, incident postmortems. Solid here? The react-patterns track is the next step — the composition, state, and boundary patterns that keep large React codebases changeable.Build with this track
Guided projects that exercise what you learn here.
Collaborative cursors
Show every connected user's live cursor and selection in a shared document, conflict-free, over WebSocket.
Command palette
A ⌘K command palette with fuzzy ranking, async action sources, and complete keyboard control (arrows, Enter, Escape, scoping) — the interaction layer every power-user tool needs.
React feature at scale
Ship one real production React feature — a live collaborative activity dashboard — then operate it: optimistic edits, streaming updates, a frame budget, full a11y, and an incident drill when a render storm freezes the tab.
Signals mini
Build a ~100-line reactive signals library (signal/computed/effect) with automatic dependency tracking and glitch-free batched updates — the same model that powers Solid, Preact Signals, and Vue 3.
Virtual data grid
Render and smooth-scroll 100k rows at 60fps with windowing/virtualization, sticky headers, and full keyboard navigation — no library, just math.
Next.js, zero to senior
Rendering strategies, App Router, server components and caching layers — production Next.js.