Once one decides to move forward with learning React, hooks are among the first things to learn (and to be frustrated with). Hooks are essential parts of React, as they were created to solve several…

Pablo_Danilo

Community Picks is a section on daily.dev where our community members share the most interesting and valuable content they've discovered online. From insightful articles to handy tools, every post is a gem curated by our dedicated coomunity. To contribute to Community Picks, you need to have at least 250 reputation points, ensuring that only active and trusted members can share their finds.

Community Picks

Learn about the usage of the useEffect() hook in React and how to optimize its usage for better performance.

React: You are Using useEffect() Wrong, Do This Instead

I found this article to be a bit vague and in some points not strictly correct though it might help entry-level/junior developers to learn something one thing or two. The good part is that writing works more as a learning than a teaching experience for the author.

I would love to see a follow up article with examples of data fetching instead of state changes. Great work!!

As someone that is quite new to React this article gave me some more knowledge to take in consideration when making a decision on building my component. Thanks for sharing!

No! useEffect is not wrong! I found that every unemployed developer is posting articles that this is wrong or this is bad just because they want to show to the recruiters that they are active. useEffect again is very good to use, but like everything there is good and bad usage

In your article, you stated…“The main idea of the useEffect hook is to synchronize data transfer with external APIs or another system, like when you are accessing a database, or waiting for an HTTP request to complete.”
That should have ended it. I think your example defeats the purpose of useEffect hook.
And with memoization, you can pass your child component into a memo() if your prop isn’t an object or function.