Frontend Mastery

useMemo vs useCallback: When optimization becomes a bottleneck

1 Views Updated 5/4/2026

React Performance Hooks

Performance optimization isn't free. useMemo and useCallback use memory to "Remember" results. If you use them everywhere, you might actually make your app Slower because the cost of checking the dependencies is greater than the cost of the re-render.

1. useMemo (Result Memoization)

Caches the **Return Value** of a function. Use it for heavy calculations:

const sortedList = useMemo(() => heavySort(list), [list]);

2. useCallback (Instance Memoization)

Caches the **Function Instance** itself. In JS, () => {} === () => {} is FALSE because they are different memory pointers. If you pass a raw function to a React.memo() child, the child will re-render every time. useCallback prevents this by keeping the pointer consistent.

4. Interview Mastery

Q: "Should I wrap every function in useCallback?"

Architect Answer: "Absolutely not. In 95% of cases, the cost of re-creating a simple function is negligible. `useCallback` should only be used when: 1) The function is a dependency for a `useEffect` in another component, or 2) The function is passed as a prop to a component wrapped in `React.memo`. Premature optimization is the root of all evil in frontend development."

Frontend Mastery
1. Core Foundation & Modern JS
ES6+ for Architects: Closures, Generators, and Symbols Asynchronous JS: Event Loop, Microtasks, and Promises TypeScript Mastery: Advanced Types, Generics, and Utility Types
2. React Internals & Core Hooks
Virtual DOM vs Reconciliation: The Fiber Architecture Effective useState & useEffect: Avoiding infinite loops useMemo vs useCallback: When optimization becomes a bottleneck useContext + useReducer: Building a built-in state manager Custom Hooks: Extracting business logic for reusability
3. Professional State Management
Redux Toolkit (RTK): Slices, Selectors, and Thunks RTK Query: Automating API caching and synchronization Zustand: The lightweight alternative to Redux Signal-based State: The future of fine-grained reactivity
4. Performance & Rendering
Component Re-rendering: How to profile and fix slow UIs Lazy Loading & Code Splitting: Shrinking your bundle size Virtualization: Rendering million-row lists efficiently Web Workers: Offloading heavy calculations to background threads
5. Design Systems & CSS
Modern CSS: Grid, Flexbox, and Container Queries CSS-in-JS vs TailWindCSS: Choosing the right styling strategy Storybook: Building a shared component library Accessibility (a11y): Building inclusive web interfaces
6. Next.js & Modern Frameworks
Next.js App Router: SSR vs SSG vs ISR React Server Components (RSC): The end of the Waterfall Data Fetching Patterns: Streaming and Suspense SEO for Frontend: Meta Tags, JSON-LD, and Core Web Vitals
7. Testing & Security
Unit Testing: Vitest and React Testing Library E2E Testing: Playwright for mission-critical flows Frontend Security: XSS, CSRF, and Content Security Policy State Synchronization: Optimistic UI & WebSockets
8. Final Polish & Interview
Micro-Frontends: Scalable architecture for enterprise teams Frontend Architect Interview: System Design & Performance