Redux Was Right for This Project. Until It Wasn't.

I'm not here to tell you Redux is dead. It isn't. But there's a specific moment in a project's lifecycle where it becomes more weight than support. I can now recognize that moment. Here's what it looks like.

vivekkumarsingh.in/blog/redux-inflection-point

Copy link

https://vivekkumarsingh.in/blog/redux-inflection-point

Share on social media

Cross-post to blogging platforms

Clicking any platform copies the canonical URL to your clipboard and opens the editor. Paste it as the article's canonical URL to keep all SEO signals on this domain.

More on this subject: Modern Web Development.

React

React Server Components Didn't Click Until I Drew This Diagram

I read the docs three times. Watched two conference talks. Still confused. Then I grabbed a whiteboard and drew the request lifecycle myself — and suddenly the whole thing snapped into place. Here's that diagram.

8 min read

React

Why I Stopped Using useEffect for Data Fetching

Every time I wrote useEffect with a fetch inside, something broke. Race conditions, stale closures, double-firing in dev mode. There's a better pattern — and once you see it, you can't write the old way again.

6 min read

React

The useCallback Trap — I Was Hurting Performance by 'Optimizing'

I added useCallback everywhere because I thought that's what good React devs do. Then the profiler showed me my callbacks themselves were the bottleneck. Memoization has a cost. Here's when it's worth paying.

5 min read

Related articles

React Server Components Didn't Click Until I Drew This Diagram

Why I Stopped Using useEffect for Data Fetching

The useCallback Trap — I Was Hurting Performance by 'Optimizing'