8 articles
Suspense and Streaming: Render UI Before the Data ArrivesSuspense lets React show fallback UI while a component waits, and streaming sends HTML in pieces. Together they kill the all-or-nothing loading spinner.
Controlled vs Uncontrolled Inputs: The React Form Decision You Keep Getting WrongEvery laggy form and 'why won't this update' bug traces back to one choice: who owns the input's value — React state or the DOM. Here's how to decide.
Keys in Lists: The Subtle React Bug You Ship Every Time You Get Them WrongUsing array index as a key seems harmless until inputs swap values, animations jump, and state attaches to the wrong row. Here's what keys actually do.
useEffect Is Not a Lifecycle Method (Stop Treating It Like One)Most useEffect bugs come from porting componentDidMount habits to hooks. Here's the synchronization model that makes effects predictable.
Most React memoization is cargo-culted and does nothing. Here's how to tell which re-renders cost you and where useMemo, useCallback, and memo earn their keep.
The React Compiler Is Stable — What Actually Changes for YouThe React Compiler memoizes your components automatically. Here's what it does, what it doesn't, and which habits you can finally drop.
After profiling 50 production React apps, the same five problems showed up again and again. None of them were exotic — and all of them were fixable.
Server Components aren't 'SSR 2.0' or a faster useEffect. Here's the mental model that makes the boundary between server and client finally make sense.
