I've been using Redux for many years so I just skipped to the last part (I'll probably read the rest tho, I'll surely learn something). Strangely, I've never no

I've been using Redux for many years so I just skipped to the last part (I'll probably read the rest tho, I'll surely learn something). Strangely, I've never normalized the data in my apps. I knew the technique but it has never been a performance bottleneck for us. But I can see how convenient it could be anyway (looking up a specific item instead of finding it). Also, we have been writings selectors but very few actually, we should definitely make it the norm. We write a lot of collection filtering, mapping and reducing directly in our connects. > Out of curiosity, anything specific in that page you found particularly helpful? I liked how you demonstrated rerendering issues (illustrated with the profiler tool) and applied those techniques (selectors, normalization) to fix them. - Just for the anecdote, slightly off-topic, I wrote like 3 years ago some Redux helper functions very similar to what you did with React Toolkit. We have 3 functions createResourcesActions, createResourcesReducers and createResourcesSagas, which take an array of strings describing our resources and return the corresponding actions, reducers and sagas (we fetch about 50 different types of resources). Something like const resources = ['users', 'posts', 'comments'] const { usersActions, postsActions, commentsActions } = createResourcesActions(resources) const { usersReducer, postsReducer, commentsReducer } = createResourcesReducers(resources) const { usersSagas, postsSagas, commentsSagas } = createResourcesSagas(resources) combineReducers({ users: usersReducer, posts: postsReducer, comments: commentsReducer }) sagaMiddleware.run(/* register the sagas */) connect(state => ({ posts: state.posts.items }), { fetchPosts: postsActions.fetchResources })(PostsList) It was funny to see you release something very similar. :) It definitely helps a lot to deal with all the boilerplate.