Realization: Putting Redux in our company framework by default was a mistake
Realization: Putting Redux in our company framework by default was a mistake.
Result:
1 People connect *every* component.
2 People embed Redux in "reusable" components.
3 Everyone uses Redux. Even when they don't need it.
4 People don't know how to build an app with just React.
I put Redux in by default so people could see how it looks and works, and to help suggest a folder and naming structure. Problem is, when Redux is there by default, people think "Oh, this is how we do React? Okay, I'll Redux all the things."
Since this caught fire, I want to clarify: Redux is great! Keep using it! 👍
The problem is Redux overuse/misuse. This problem is caused by insufficient training about how to use plain React state, and when to reach for Redux.
Here's a relevant 3 minute clip in my React and Redux @pluralsight course: "Do I need Redux?" https://app.pluralsight.com/player?course=react-redux-react-router-es6&author=cory-house&name=react-redux-react-router-es6-m5&clip=1&mode=live