Learn React in 2020 (6 Part Series)
At this point, there’s nothing stopping React.
According to Hacker News trends for 2019, React has maintained the #1 spot for most in-demand tech skill a developer can have, beating out Python for the third year in a row.
But React's popularity isn't limited to just employers—developers themselves are downloading and building projects with React nearly 3 million times per week.
What do these numbers tell us?
Learn React. There's never been a better time.
If you're new to React, welcome! You're in the right place and you're getting started at the perfect moment.
And if you're already a developer, adding React to your set of skills will further your career and broaden your prospects in the future.
I can say without reservation that nothing has advanced my career more than making a commitment to learning React, deeply.
How did I do that, exactly?
More on that in a moment...
If you've tried to learn React in the past you may have felt at times, “I can't do it. React is too difficult!”
And you wouldn't be alone in this feeling.
I was in the very same position.
A few years ago, I hardly knew what React was, but I saw the growing interest around it and figured maybe it was something worth learning.
And then I made something you likely already have—a resolution, a commitment to learn it for good.
At that time, I was in a completely different career path. But I worked hard, learning and writing React code whenever I could.
I read articles, watched tutorials, I copied the code I saw others write, I coded on my own whatever I could, and took notes all along the way.
And after about 6 months of hard work... things finally started to click.
- I moved on to being able to build apps on my own, without needing to rely on guided tutorials, only resorting to Google to resolve the problems I couldn't fix myself.
- I got involved in building compelling projects and started working with React everyday. (I still do, to run my business, Code Artistry).
- I was even offered a job to lead the redesign of the home page of a Fortune 100 company(!)
But despite the progress that I had made, things had clicked not for the reasons I expected...
It wasn't the hard work that I put in that made the results for me—it was knowing the most important thing is not what you learn in React, but how you learn it.
Learning React then was largely the same as it is now. There are tons of articles, tons of training courses that developers release every day, meaning more information to help you learn all the time.
And this is excellent. Plus there are more React developers today than ever before, many of whom are making their knowledge publicly available.
You'll find so much technical content, but almost no guidance from those same professionals about how important each tool or concept is for you to learn.
Without a blueprint for how to learn these technologies, meaning how much time you should dedicate to learning each concept, and how they fit into the big picture of becoming and working as a developer, you are set up for a great deal of difficulty and wasted time.
This is something that often led me astray in learning React—
I would read an article, go off and dedicate time simply trying to learn the tool the article featured (say, TypeScript). As I did, I got frustrated along the way, because I would often spend a day or more learning a tool that was too difficult and secondary to other skills I should have been working on instead.
I'm here to ensure you don't run into the same difficulties that I did.
I want to put you on the fast track to doing what you want with React, in your quest to get a developer job, code amazing apps, and open up totally new avenues in your career.
But before we go forward, let’s take a quick step back to answer some essential questions:
- Why is React so popular in the first place?
- And how did React come to be such a necessary library for businesses and programmers alike in the current tech landscape?
React’s popularity has to do with a significant change in making web sites in recent years.
Traditionally, web sites worked—and a lot still work today—by your browser getting HTML from a server, and then displaying each page with that HTML. And whenever you go to a different part of the site, the browser will do a full refresh, it will get more HTML from the server, and that new page will be displayed (rendered) with the new HTML.
In a word, websites are traditionally server-side rendered.
But as time progressed, developers converged on a different pattern for building web sites, called web apps.
What’s the difference?
There’s really no strict difference, but the term "web app" came about to describe these web sites which were made to be more interactive and perceptibly faster.
What was the innovation?
This, as compared to server-side rendering, is known as client-side rendering.
The advent of client-side rendering and the desire to build these snappier SPAs resulted in a push among many companies to figure out how to best create this new type of app, including the company Facebook.
React was not an overnight success, however.
In fact, it came as a shock to developers upon its release.
It was startling in that it challenged what was established as "best practices" for a long period of time in web development.
The logic behind this concept was that programmers could more clearly reason and develop each part of their project with such divisions in place.
React threw that right out the window.
And unsurprisingly, React was not well received at first by the developer community.
But with time and by using React in real-world projects, what started as an unwelcome change came to be gradually embraced as a powerful new way of uniting all of the necessary parts of any web application.
And this is React in a nutshell—a library born out of the need to make a new kind of app, which in the end, totally changed the way that developers use the core technologies of the web.
And starting now, we're going to cover how to learn React in a transformative way.
I'm excited to announce that over the next two weeks, I'm putting together a series on how to learn React from the ground up in record time. And you're reading the first article in that series.
Along the way, we'll cover immensely practical tips you can start using to supercharge your React learning process.
Here's some of what's in the pipeline:
- How you can start thinking like a React developer right away
- What coding concepts will put you on the path to success and which ones you need to set aside
- Plus one piece of advice that will make you irresistible to future employers
In the end of this series, I want to put you on the right path to learning React, so you can do what you want with it.
1) Sign up for the rest of the series right here.
We've just scratched the surface, but you won't be able to make the most out of the content in this series without the rest of the articles to get the complete picture.
Reserve your spot on the list now so you don't miss out.
2) Before I release the next article, head over to my site, Code Artistry, and send me an answer to the following question:
"What is your biggest pain point when learning React?"
So reach out to me, and I may be able to directly address your issue in this series.
Also, if you love what this series is all about, be sure to share this article to someone you know who would benefit from the information in this series. They'll thank you for it.
Finally, I want to congratulate you. Learning React is a big commitment, but it’s a worthy one that will pay dividends in the long run.
Keep at it and I’ll catch you in the next article!