r/javascript • • Jul 11 '17

help What 10 Things Should a Serious Javascript Developer Know Right Now?

I'm inviting pure opinion here, but what's your list of ten things that everyone looking for a good javascript role should know and understand. Personally, I'm in a role where what I know is adequate, but I want to be somewhere better; somewhere that has some flippin standards. I'm learning outside of work requirements at the moment, but there is so much shit to learn out there.

The objective is to do good work in a good place.

Narrow it down to your ten for me, or for you.

Can be your own "I must learn x" list too. I'm very interested to hear what people think.

348 Upvotes

223 comments sorted by

View all comments

8

u/ProdigySim Jul 12 '17

I don't know anyone who is specifically a "Javascript Developer". Most people I meet are organized by discipline / stack layer rather than language used.

But, for web development which includes Javascript, I'll name a few things I think are important outside of other stuff mentioned here:

  1. Caching: There are multiple ways to do HTTP caching (etags vs hard expiration). A speedy web app will utilize static assets via CDN as well as live data sets. Being able to boot a web app with appropriate caching, while avoiding cache poisoning, and being able to invalidate cache or update references sanely is pretty important for performance.

  2. Perf Auditing: Putting aside standard algorithmic complexity stuff, when trying to speed up an existing application being able to use Js Perf tools is pretty important. The Chrome Dev tools have a lot available here, but take some practice and learning. Being able to discern & solve JS parse time, resource lock delays, slow JS execution, inefficient DOM interaction, and long paint triggers is a tricky advanced skill.

  3. Build System: Tons of JS projects use build systems, and for a medium to large application you're probably going to need one. I don't care if you webpack or gulp or shell script, but being able to put together & scale a sane build system is a pretty important tool!

I don't want to think of 10 things but as a final thought:

Have an opinion on a framework or two: There's lots of popular frameworks out there, there are also great niche frameworks. They can all solve a lot of the same problems, and some can solve more specific ones. Choosing a popular framework is a safe bet, but having an understanding opinion on one or more will help you face shortcomings of the frameworks and evaluate new ones as they come.

Also +1 to building sane REST APIs. Even the big companies screw these up every once in a while, so put your best foot forward every time you design one.

1

u/[deleted] Jul 12 '17

These are good points. You're right about javascript developer being a less typical job title, though I do see it in job ads more and more. In my case, I have a firm handle on the other parts of the frontend stack, but the javascript can seem a bit Looney Tunes some days.

1

u/YooneekYoosahNeahm Jul 13 '17

It's a bit late but got any favorite resources on those advanced perf auditing points?

1

u/ProdigySim Jul 13 '17

I don't have any great tutorial videos or anything, but the Chrome official documentation is fairly complete.