---
title: "Discussion on \"How to Avoid Overusing useCallback and useMemo in React\" | Hashnode"
description: "Discussion on \"How to Avoid Overusing useCallback and useMemo in React\". If you've spent enough time in the React ecosystem, you'll have likely seen codebases where nearly every function is wrapped with useCallback and the computed value is wrapped with useMemo.\nThe reason"
url: "https://hashnode.com/posts/how-to-avoid-overusing-usecallback-and-usememo-in-react/6a32f4091d5034aa7d96e448"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [How to Avoid Overusing useCallback and useMemo in React](https://freecodecamp.org/news/how-to-avoid-overusing-usecallback-and-usememo-in-react?utm_source=hashnode&utm_medium=feed)

If you've spent enough time in the React ecosystem, you'll have likely seen codebases where nearly every function is wrapped with useCallback and the computed value is wrapped with useMemo. The reason

Jun 17 · 26 min read · freecodecamp.org  
Read the article

-   [#reactjs](https://hashnode.com/tag/reactjs)
-   [#performance-optimization](https://hashnode.com/tag/performance-optimization)
-   [#memoization](https://hashnode.com/tag/memoization)
-   [#reactmemo](https://hashnode.com/tag/reactmemo)

## Written by

[Olaleye Blessing](https://hashnode.com/@Jongbo)

@Jongbo · Lagos, Nigeria

  
[View profile](https://hashnode.com/@Jongbo)

Senior Frontend developer

Frontend Developer | Open-source contributor | Experienced Backend Developer

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
