Maybe this is because I'm a "developer[] unfamiliar with class-based OO paradigms" but I find hooks components easier to read later. You start at the top, read

Maybe this is because I'm a "developer[] unfamiliar with class-based OO paradigms" but I find hooks components easier to read later. You start at the top, read to the bottom, and assuming you can catch crazy indirection within a hook callback during review, that's what happened. No HOCs. No having to memorize an externally documented lifecycle order. No having to cross-reference methods against the state they update 50-60 lines up the file. I'm genuinely curious if the difference is because I was doing tons of Recompose/HOC style components before hooks came out. Also, just FYI, it didn't click for me until this tweet[1]: > The question is not "when does this effect run" the question is "with which state does this effect synchronize with" > useEffect(fn) // all state > useEffect(fn, []) // no state > useEffect(fn, [these, states]) [1] https://mobile.twitter.com/ryanflorence/status/1125041041063665666 https://mobile.twitter.com/ryanflorence/status/1125041041063...