Web development is huge. What should you learn next?

Web development is huge. There's just so much to learn. It's not only a matter of learning CSS, JavaScript, and HTML, but a matter of learning Backbone.js, Angular, Flexbox, React, Ember, Web Animations, Bootstrap, Express.js, Rails, jQuery, Sass, Node.js, and CoffeeScript. Holy shit, right? And these are just the ones that I pulled from Code School. Go to other websites and you might find a different set of things that you should learn.

And you know what? This is on top of actually building the website whilst dealing with browser inconsistencies, different screen sizes, and accessibility. Oh, and bugs. 🌚

So when you just learned one piece of technology, what do you learn next?

The lowly web developer doesn't stand a chance. Or does she? Here are three things that I learned over the last few years to deal with figuring out what to do next:

Get used to this feeling

This feeling of not knowing enough will always be with you because you will never reach a point where you know everything. And I'm not trying to be a downer—this is actually good news! There's so much technology out there that no one ever knows everything. So be comfortable with this feeling because not knowing enough is ok.

Remember that you will always be a student. So keep an open mind about things.

Learn with purpose

One of the best ways to learn, in my opinion, is just-in-time learning. It's learning about a certain thing or technology before diving into a project (whether it's at your job or it's your personal project). For example, a few weeks ago, I decided that I want to contribute to this open source project that uses React. Since I don't know React, I dove in to learn the basics so that I at least know what's going on in the code.

Actually, I took a video of me learning React and diving into the project! And soon, I was using it for my personal (silly) projects.

Steal websites

Another variant of just-in-time learning involves some detective work. It's stealing websites. I wrote about this a while back, but the gist is that if you like a certain website or a certain widget in a website, try to figure out how it's made by using DevTools.

And that's it! If you think I missed something or if you have better tips for people, please tweet or email me!

Additional Resource

Here's a good podcast that's related to this: https://overcast.fm/+FJC0Vua8E. I hope you like it!

Enjoyed this article? My newsletter is pretty dope, too.

Comments