If you came to React from another front end technology, you might have observed that React is very unopinionated. This is good because you can really design an application however you want, but it's also bad because you can design an application however you want. A good way to ensure you're writing React code in a way that it was intended to be written is to understand React's core philosophies.

2015 was the year React took off and with it came many different patterns (some great, some not so great) to do the same thing. Luckily, the React community is starting to settle on best practices and this blog post does a great job of summarizing all of those.

Tutorials

The biggest complaints I hear about React are related to tooling/setup, and testing. Lucky for you Spencer elegantly walks through how to set up a React project and test said React project in this tutorial. If you're new to testing in React and want another perspective, check out this post.

Resources

You've most likely been in the position where you just want to execute some small piece of React code without having to set up the whole boilerplate. Well, now you can. React.run gives you an in browser React environment to execute your React code. Think of it like JSFiddle for React, if you will.

Videos

The definition of "legacy code" can be described simply as "code that doesn't have tests." Code you just wrote, 5 minutes ago? Legacy code. Code that can't be refactored, but only changed. How do we prevent the mountain of legacy code that most projects become? A solid testing strategy. In this video series Trevor will dive into testing React applications. From getting setup and running tests, all the way through testing Redux enabled React applications. You will need a premium egghead account to access these, unfortunately.