DEV Community

Discussion on: I Just Didn't Get Redux!

Collapse
 
markerikson profile image
Mark Erikson

Hi, I'm a Redux maintainer.

Out of curiosity, did you try looking at the official Redux docs at all during this process? If yes, do you have any feedback on how they did or did not help you? We're currently planning a major revamp of the docs, and I'd love to know how we can improve them.

If you didn't look at the docs, was there a particular reason why not?

The "teaching Redux + React-Redux" thing is a valid point that I've seen come up a number of times. On the one hand, given that Redux is primarily used with React, it's reasonable to teach connect() right away. Dave Ceddia's Complete React Redux Tutorial takes that approach.

On the other hand, you can use Redux without any UI layer (or framework) at all, and doing that work "by hand" may help make it more obvious what's going on. The slides for my "Redux Fundamentals" workshop try to take that "ground up" approach, including showing how you would have to manually integrate Redux with React if you weren't using connect(). (My post The History and Implementation of React-Redux also goes into details on just what connect() does internally and why it's needed.)

I've got one big suggestion I'd like to offer. Please check out our new Redux Starter Kit package. It includes utilities to simplify several common Redux use cases, including store setup, defining reducers, immutable update logic, and even creating entire "slices" of state at once:

redux-starter-kit.js.org

Hope that helps, and please let me know if you've got any questions I can answer!

Collapse
 
edlinkiii profile image
Ed Link III

Honestly, no, I didn't consult the official Redux docs. As I stated in my post, I didn't even realize it was a stand alone library until I the I ran into it on FreeCodeCamp.

Thanks for the resources you provided, I'm sure they will come in handy as I'm implementing all that I've been learning recently.

Collapse
 
markerikson profile image
Mark Erikson

Yeah, as a general suggestion: whenever you do start trying to use any library, it helps to go straight to the official docs and repo right away. There are certainly some great tutorials for all tools that have been written by their community and users, but it's also good to see how a tool describes itself and how it should be used.

Collapse
 
roeltf profile image
Roel Torres

Hello! I'm very interested in learning Redux and have tried a couple times to do the tutorial from the official docs but I still lack an understanding or general idea of how redux works. I've been at it for only a couple of weeks and i'm not a developer, just learning, but I would love to know how I could be of any help or just follow along with the revamp of the docs. Thanks :)

Collapse
 
markerikson profile image
Mark Erikson

Hiya! Given your description, I think the best way to contribute would be to if you could go through the current tutorial pages, write down everything that you find particularly confusing or hard to understand, and add a comment to this thread listing those thoughts:

github.com/reduxjs/redux/issues/3313

That will help us think about better ways to explain things.

Also, if you read through some of the other tutorials that I linked in the parent comment, do any of those explanations "click" better for you? If so, please let us know what other explanations you found easier to understand.

Thread Thread
 
roeltf profile image
Roel Torres

Will do! Thanks for your answer :D I'll read the thread and check out the tutos on your parent comment so I can start commenting. Thanks again!