Thinking in render cycles, not components

This is placeholder content for a future post about diagnosing unnecessary re-renders in React applications before jumping straight to memoization.

The real version will walk through using the React DevTools profiler to find which component actually owns the state change, and why fixing the source is usually better than wrapping the symptom in useMemo.

It will also cover referential equality, functional state updates, and when splitting a component actually helps versus when it just moves the problem.