Why React Components Re-Render (And When You Should Actually Care)
Most React performance advice is applied to problems that do not exist. Here is what actually triggers a re-render, when it matters, and how to fix the cases that genuinely hurt.
Archive
27 posts published this month.
Most React performance advice is applied to problems that do not exist. Here is what actually triggers a re-render, when it matters, and how to fix the cases that genuinely hurt.
New parents are told babies sleep a lot and then discover they sleep in fragments, at unpredictable hours. Here is what is actually normal, and what genuinely helps.
Total hours is a poor measure and a worse argument. Focusing on sleep, displacement and what is actually happening on the screen produces better outcomes and fewer rows.
Static, server-rendered, client-rendered or streamed — Next.js gives you all four, per route. Here is what each one costs, what it buys, and how to choose without guessing.
The activities children remember are usually cheap, repeated and slightly unstructured. Here are ideas that cost nothing, plus why the expensive day out often disappoints.
LCP, INP and CLS measure loading, responsiveness and visual stability from the user's point of view. Here is what each one really measures and the fixes that reliably move them.
An emergency fund is the least exciting financial product in existence and the one that prevents the most damage. Here is how much to hold, where to keep it, and how to build one.
An index fund buys the whole market instead of trying to pick winners. Here is how that works, why costs matter so much, and what the approach cannot protect you from.
Flexbox and Grid solved layout properly, and container queries finished the job. Here is when to use each, plus the modern CSS that quietly removed the need for most utilities.