Blog

Every form input in React has a value, and something has to own it. Either React holds the value in state and pushes it into the input on every rende

A surprising number of React bugs come from the same root cause: storing a value in state that could have been calculated from other values. A filter

Fetching data in React looks simple until you ship it. A useEffect with fetch and two pieces of state works for a demo, then the real questions a

Recoil introduced many React developers to the idea of atomic state: small, independent pieces of state that components subscribe to individually

Picture a dashboard where a filter in the sidebar, a chart in the middle, and a summary card in the header all depend on the same few pieces of state

Most React apps reach a point where useState and props stop being enough. A cart count in the header, a sidebar toggle shared across layouts, or a