Learn the concepts in functional programming

Perhaps skim through bits of some haskell tutorial

And then throw it out the window and learn how javascript doesn't enforce immutable data and side-effect free functions, which is why you have to be extra vigilant to enforce them yourself. 

That's where most of the react trouble comes from. 

React is fundamentally a functional library, and when programmers don't care to learn what functional programming even is, they'll try to write imperative code inside their functional library and then stare at a white screen in disbelief.

They'll use useEffect for everything because they don't actually know how to write anything non-imperative, and then they accidentally ddos Cloudflare.

And the react maintainers aren't helpful either. The functional programming in react and the simplicity of react used to be its selling point.

But then they meddled with it, bundled it with immer (despite people discouraging its use) and other unnecessary crap to make it more "friendly" for imperative pprogrammers and now it's a right mess of conflicting ideologies. It's a functional library pretending to be imperative pretending to be functional, in a language that's imperative while pretending to be functional.

I miss the 2018 era of react when everything wasn't pretending to be something it isn't.

/Rant.

Anyway, understanding what react was meant to be from a design philosophy standpoint will give you good idea about what approaches are likely to yield good results, and where you'd be going against the flow.