Where should you invest your time to get the most benefit? Which tech stacks are companies hiring for right now? Which ones have the most growth potential?
What are the most important technologies to know right now? This post is a high-level overview of stuff you need to know, packed with links where you can learn all about it.
A Note on Optional Learning
Some of this stuff is strictly optional*, which means, I recommend them if you are interested in them, or you need to know them for a job, but you should not feel obligated to learn them. Anything marked with an asterisk (e.g., example*) is optional.
Anything not marked with a * should be learned, but don’t feel obligated to learn everything there is to know about everything. You need to be aware of the non-optional stuff, but you don’t necessarily need to be a definitive subject matter expert on absolutely everything.
- Partial application & Curry
- Builtin methods: Learn methods for the standard data types (especially arrays, objects, strings, and numbers).
- Callbacks: A callback is a function used by another function to signal when there is a result ready. You say, “do your job, call me when it’s done.”
- Promises: A promise is a way to deal with future values. When a function returns a promise, you can attach callbacks using the
.then()method to run after the promise resolves. The resolved value is passed into your callback function, e.g.,
doSomething().then(value => console.log(value));
- Ajax & server API calls: Most interesting apps eventually need to talk to the network. You should know how to communicate with APIs.
- Classes (note: Avoid class inheritance. See How to Use Classes and Sleep at Night.)
- Generators & async/await: In my opinion, the best way to write asynchronous code that looks synchronous. It has a learning curve, but once you’ve learned it, the code will be easier to read.
- Performance: RAIL — Start with “PageSpeed Insights” & “WebPageTest.org”
- Progressive Web Applications (PWAs): See “Native Apps are Doomed” & “Why Native Apps Really Are Doomed”
- Chrome Dev Tools: DOM inspect & JS debugger: The best debugger, IMO, though Firefox has some really cool tools you might want to check out, too.
- git & GitHub: Distributed version manager — keeps track of your source code changes over time.
- Babel: Used to compile ES6 to work on older browsers.
- Atom, VSCode, or WebStorm + vim: You’re gonna need an editor. Atom and VSCode are the most popular JS editors today. Webstorm is another solution with very robust support for quality tooling. I recommend learning vim, or at least bookmarking the cheat sheet because sooner or later, you’re gonna need to edit a file on a server, and it’s the easiest way — vim comes installed on just about every flavor of Unix compatible OS, and works great over SSH terminal connections.
- ESLint: Catch syntax errors and style issues early. After code review and TDD, the third best thing you can do to reduce bugs in your code.
- Yarn*: Similar to npm, but install behavior is deterministic, and Yarn aims to be faster than npm.
- React takes inputs to components as props and conditionally renders DOM updates if data has changed for specific parts of the DOM. Data updates during this phase can’t retrigger the render until the next drawing phase.
- Event handling phase — after the DOM has rendered, React automatically delegates DOM events to a single event listener at the root of its DOM tree (for better performance). You can listen for events and update data in response.
- Using any changes to the data, the process repeats at 1.
This is in contrast to 2-way data binding, where changes to the DOM may directly update data (e.g., as is the case with Angular 1 and Knockout). With 2-way binding, changes to the DOM during the DOM render process (called the digest cycle in Angular 1) can potentially retrigger the drawing phase before the drawing is finished, causing reflows and repaints — slowing performance.
React does not prescribe a data management system, but a Flux-based approach is recommended. React’s 1-way data flow approach borrowing ideas from functional programming and immutable data structures transformed the way we think about front-end framework architecture.
For more on React & Flux architecture, read “The Best Way to Learn to Code is to Code: Learn App Architecture by Building Apps”.
- create-react-app*: The quickest way to get started with React.
- react-router*: Dead simple routing for React.
- Next.js*: Dead simple Universal render & Routing for Node & React.
- velocity-react*: Animations for React — allows you to use the VMD bookmarklet for interactive visual motion design on your pages.
Redux provides transactional, deterministic state management for your apps. In Redux, we iterate over a stream of action objects to reduce to the current application state. To learn why that’s important, read “10 Tips for Better Redux Architecture.” To get started with Redux, check out the excellent courses by the creator of Redux, Dan Abramov:
Redux is mandatory learning, even if you never use Redux for a production project.
Why? Because it will give you lots of practice and teach you the value of using pure functions and teach you new ways to think about reducers, which are general-purpose functions for iterating over collections of data and extracting some value from them. Reducers are so generally useful that
Array.prototype.reduce was added to the JS specification.
Reducers are important for more than just arrays, and learning new ways of working with Reducers is valuable all by itself.
- redux-saga*: A synchronous-style side-effect library for Redux. Use this to manage I/O (such as handling network requests).
Angular 2+ is the successor to the wildly popular Angular framework from Google. Because of it’s crazy popularity, it’s going to look great on your resume — but I recommend learning React first.
I have a preference for React over Angular 2+ because:
- It’s simpler, and
- It’s extremely popular and used in lots of jobs (so is Angular 2+)
For this reason, I recommend learning React, but I consider Angular 2+ strictly optional*. If you have a strong preference for Angular 2+, feel free to swap them. Learn Angular 2+ first, and consider React optional. Either will benefit you and look great on your resume.
Whichever you choose, try to focus on it for at least 6 months — 1 year before running off to learn the other one. It takes time to really sink into strong proficiency.
As much as I love RxJS, if you just import the whole thing all at once, it can really bloat your bundle sizes (there are lots of operators). To combat bundle bloat, don’t import the whole thing. Use the patch imports, instead:
Using patch imports can reduce the size of your rxjs dependencies in your bundle by ~200k. That’s a really big deal. It will make your app much faster.
EDIT: Why Didn’t You List <your favorite thing>?
Several people have asked why I didn’t list their favorite framework. One of the important criteria I considered was “will this be useful on a real job?”.
Yes, this is a popularity contest, but the opportunities that knowing a framework will open up is an important consideration when you’re deciding where to focus your learning investment.
To answer that question, I looked at some key indicators. First, Google Trends. If you want to reproduce this Google Trends graph, remember to select by topic, not keyword, since several of these words will deliver lots of false positives. In other words, these are topic-focused trends, not keyword searches:
What this tells us is relative interest in various projects. If people are searching for them, chances are they’re exploring their options, or searching for help or documentation. This is a pretty decent indicator of relative usage levels.
Another good source of data is Indeed.com, which aggregates job listing data from a large variety of sources. Job posting popularity has declined sharply in recent years, but they still collect enough data to make good relative comparisons that tell you frameworks that people are actually using in production projects, on the job:
Angular and React dominate: Nothing else even comes close. (Except jQuery, which is used on a huge share of all websites — non-apps included — because it’s used by almost all legacy systems, including popular CMS systems like WordPress).
You might see that Angular has a significant advantage over React in these listings. Why do I recommend learning React first? Because:
- More people are interested in learning React than Angular
- React significantly leads Angular in user satisfaction
In other words, React is winning the mindshare and customer satisfaction battles, and if the trends over the past year and a half continue to unfold, React has a very real chance of unseating Angular as the dominant front-end framework.
Angular 2+ has a chance to turn that around, so Angular could make a comeback, but so far, React is putting up a really good fight.
Frameworks to Watch
- Vue.js* has a ton of GitHub stars and downloads. If things continue the way they are going, it will do very well in 2017, but I don’t think it will unseat either React or Angular (both of which are also growing fast) in the next year or so. Learn this after you have learned React or Angular.
- MobX* is a great data management library which has become a popular alternative to Redux. It is also growing fast, and I expect it will also do well in 2017. I prefer Redux for most apps, but there are definitely cases where MobX is a better choice. For example, if you have hundreds of thousands of dynamic DOM objects on a page, it will probably perform better. Also, if your app workflows are all simple and you don’t need transactional, deterministic state, you probably don’t need Redux. MobX is definitely a simpler solution. Learn this after you have learned Redux.
He enjoys a remote lifestyle with the most beautiful woman in the world.