Don't forget "functions that do totally normal things now need to be rewritten as a hook".
Hooks are for stateful code.
Easiest way I put it to my team was that in order to qualify as a hook, it must consume a hook.
const [sortedValues, setSortedValues] = useState([])
useEffect(() => {
setSortedValues(values.sort())
}, [values])
It is unfortunate that useEffect is too powerful of a escape hatch that people forget it IS a escape hatch and should be avoidedTo be honest I much prefer hooks than old class-based state manipulation, but it does require deeper understanding of the React, JS and state to get right.