5 things I learned about React.Js

Before starting my journey at a coding bootcamp in Toronto, the only thing I knew about React was that Facebook made it.

It was just another library in a massive pool of libraries. However, I constantly read about how great it is and about this cool thing called JSX. Apparently it shocks most developers at first because it mixes your HTML into your Javascript (completely opposite of how we’ve learned to code).

When you think about it, it just sounds messy, but React has done a great job of making it feel natural, and you grow used to it very quickly.

Take a look at Stack Overflows 2017 Developer Survey to see just how happy people are with React.

As someone who’s new to React, i’m quickly becoming familiar with it, and really enjoy and see the massive potential. With my coding bootcamp ending soon, the ideas are spinning through my head for what I can make.

With that said, I’ve learned a lot about React, but I’d like to share the fundamentals of what I’ve learned and still trying to grasp.

1. React is very reuseable

My favourite thing about react is how easy it is to make reuseable code. Components can be built from the ground up and used all over your site. In a way React reminds me a lot of BEM in that with BEM you can plop class names everywhere, and your site can come together really fast.

2. It has great documentation

I find one of the hardest things about React is figuring out the way the data flows. Where do I add State? Where do I add props? I feel like this is something i’ll struggle with for a while, but React has great resources like here: https://facebook.github.io/react/docs/thinking-in-react.html which help my brain a little bit.

3. The React developer tools saves a lot of headaches

We’re used to the developer tools for regular websites, and how they can help you work out a bug. Luckily React also has developer tools: https://chrome.google.com/webstore/detail/react-developer-tools/fmkadmapgofadopljbjfkapdkoienihi?hl=en

Today I was stuck on something for a lot longer than I’d like to admit, but after looking at the React developer tool, I found the bug in seconds. All of my pain was caused by one uppercased letter. I appreciate all the pain from bugs like this though, because I typically don’t get caught by them again.

4. React is amazing with Firebase

In my recent React project, I learned to create a cloud database with Firebase. At first I was overwhelmed learning two new technologies at once, but now I really appreciate how well the two work together. Creating a login and authenticating is a lot easier than I could’ve imagined and Firebase is free, with a generous amount of space.

5. It’s not good in every situation

From what I’ve gathered (and it makes a lot of sense), React isn’t meant for every site. React excels at 1 page web apps, but it might be way overboard to make a site using React for the local window cleaner.

React would be great for a more ambitious app that has multiple people working on it. Or a cool api project that changes views without reloading like a netflix clone.

I’m still really new to React and even web development, but I’m trying to pick up a little bit at a time and really understand it.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.