just wanted to say that you are not the only one being lost in react and redux. redux is a pain in the ass for me
Listen to the podcast by Toolsday: #77 Is Redux Dead?
There is this new trend or not so new, where new projects are moving away from Redux.
I thought of sharing some of my experience. when i was following react redux challenge , I always think why redux? why should i learn this. because in react we can mange state and in redux we can mange state. then what kind of problem redux try to solve. finally I understood that. when you have many component if you have redux to manage state, it is so easy. . there is channel on youtube. the name of the chanel is ninja. in that channel he has a tutorial about react redux firebase node. he is amazing to teach. if you watch that video , all problem will be solved.
if you have multiple component and if you want to pass the state, it is little confusing to pass your state to that component through props. once you understand redux, you may hate react state management system .
go to youtube and search for reac ninja. you can see complete react with redux tutorial, watch all that video tutorial. then the next tutorial you can see on the same channel is react redux firebase. just watch this video till 15th episode. i am sure after that you handle react well. you should code along with him. watching that video tutorial like watching movie does not make any difference. he was the one who taught me how to use reduce. what ever you do, if you feel like you dont understand, do console.log which teach you whole java script .
Feeling lost, overwhelmed, frustrated and that you don’t know enough is something you grow used to as a developer. But if you fall in love with coding, you literally work past any imposter syndrome or roadblocks and keep going.
For example, a lot of react is syntax.
class YourComponent extends React.Component { }
Even now I can’t explain word for word why this is so and frankly I am not good with technical definitions. Took me a while to understand the term chaining and I was doing it long before I understood how to explain what my code was doing.
However, if you start to understand how it works, start to understand constructors, grind through state, fetching data from APIs and AJAX, as well as create more projects you will slowly start to understand the framework and the react life-cycle intuitively and that’s what counts.
Doing more and getting numb with the discomfort of not knowing everything.
A lot of development is repetition, syntax and experience. As you build more, you just intuitively understand what the syntax does, understand behaviors, bugs, and so on.
And to me, building apps is more important than the etmology and it’s like learning a language. Don’t try to understand everything and be able to explain everything when you start out. Instead, ride the waves, try to make mistakes and create.
Via repetition, NOT an amazing spoon fed tutorial or definition, you WILL get it.
2 Likes
My biggest complaint about the REACT challenges so far, is that the explanations are usually too short, and I have no idea what they’re looking for, so then I have to look at the answers, which is annoying. Their best challenges are when they work out a VERY similar problem in the lesson. Maybe different coders wrote these REACT challenges? It’s a bit like trying to learn Chess from a GrandMaster who doesn’t remember what it was like as a beginner.
3 Likes