Skip to content
Vivek Kumar SinghVivek Kumar Singh
Hire

Share this article

React

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

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

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.

vivekkumarsingh.in/blog/usecallback-was-making-things-slower

Copy link

https://vivekkumarsingh.in/blog/usecallback-was-making-things-slower

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.

Related articles

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

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
Why I Stopped Using useEffect for Data FetchingReact

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
Building a Component Library Your Team Won't Quietly AbandonReact

Building a Component Library Your Team Won't Quietly Abandon

Most internal component libraries are created with good intentions and abandoned in six months. I've seen it twice. Here's what we did differently the third time — and the one decision that changed adoption.

9 min read