My biggest mistake these last few weeks was taking the same approach with React as I did with Javascript HTML, and CSS. I kept hearing and reading about how one was Imperative while the other was Declarative and it made sense. React seemed like it would definitely be the easier approach to creating the front end of an application. Each topic made enough sense in its own. Create parts of your application in components, pass data with props and states, use CSS to make it look how you want and let React do the rest.
Each topic made sense on its own, but the issue was the process to accomplish each task in React was a little more complex. I was so used to not memorizing processes, rather being able to logic through what it is I want to do. The same should be done with React as well, but only after you've memorized each individual process. During my labs I knew what I wanted to do, but I spent so much time looking back on syntax that I often lost my train of thought and couldn't keep track of what I wanted to do. I found myself coming just short of completing the labs and even accomplishing That definitely put into perspective for me what the difference between a good coder and great coder is. If you're able to focus to on the grand scope of your project, you’ll be able to make it with more depth, therefore smoother and better. When you have to constantly look back just to remember how to send up data using a callback function, the grander ideas become seemingly more impossible. My biggest advice to anyone wanting to learn React, in a short period of time especially, take your time learning each and every process. Knowing the general logic is easy enough, truly understanding why you’re writing each line of code the way you are is not so easy. Pattern matching seems like it would be the right approach, but then you're limited because of yourself. Anything you can't find a pattern to associate with becomes too difficult. Learn the processes and then understand why you're doing it that way.
Top comments (0)