Course contentsShow
← React
Lesson 907 of 2,39623. useMemo and useCallbackFree lesson

The Readability Tax

How excessive memoization clutters code with dependency arrays and makes logic harder to follow and maintain.

The Readability Tax

What you'll learn: How excessive memoization clutters your code with dependency arrays and makes it harder to understand and maintain.

The Hidden Cost of Over-Optimization

You've learned that useMemo and useCallback aren't free — they have a performance cost. But there's another cost that's often more damaging: readability.

Every time you wrap something in useMemo or useCallback, you add visual noise. You add a dependency array that future developers (including you) must mentally parse. You create opportunities for bugs when dependencies aren't listed correctly.

What It Looks Like

Without memoization, code is straightforward:

function UserProfile({ userId, filter }) {
  const greeting = `Hello, user ${userId}`;
  const handleClick = () => console.log('Clicked');
  const isActive = filter === 'active';
  
  // Simple, readable logic
}

With aggressive memoization:

function UserProfile({ userId, filter }) {
  const greeting = useMemo(() => `Hello, user ${userId}`, [userId]);
  const handleClick = useCallback(() => console.log('Clicked'), []);
  const isActive = useMemo(() => filter === 'active', [filter]);
  
  // Same logic, but harder to scan
}

The second version doesn't just cost performance — it costs cognitive load. Every reader must ask: "Why is this memoized? What am I missing? Is the dependency array correct?"

When the Tax Is Worth Paying

The readability tax is justified when you've measured a performance problem. But for most code, clean and simple beats optimized and cluttered.

Key Takeaway: Memoization makes code harder to read and maintain. Only pay the readability tax when profiling proves you need to.