Are you tired of being....tired?

4 tips to resist JavaScript fatigue

Gabriela Motroc
JavaScript fatigue
Businessman sleeping near monitor image via Shutterstock

JavaScript fatigue initially revolved around React but it eventually started to spread and swallowed the entire JavaScript community. Being a bandwagon jumper and trying to use all the latest tools will inevitably lead to JavaScript fatigue, but here is how to resist it.

JavaScript fatigue might as well be this year’s buzzword as the JavaScript community is going through emotional turmoil due to an avalanche of new frameworks and techniques. The easiest way to resist this type of fatigue is to ask yourself if you are focusing on the right things or if the frameworks you master are the best out there.

The phrase JavaScript fatigue refers to the idea that by choosing React, “you’ve unwittingly opted into a confusing nest of build tools, boilerplate, linters, and time-sinks to deal with before you even get to create anything,” Eric Clemmons, the creator of React Resolver wrote in a blog post in late 2015.

SEE ALSO: Choosing the right JavaScript framework

JavaScript fatigue can easily be avoided if programmers exercise restraint and self-discipline and understand the nature of JavaScript. Shifting away from the features that are no longer needed is the best thing to do, but this action that could switch off fatigue is one tough choice. Once you’ve started to ask yourself repeatedly if that feature should be ignored or used there’s no turning back. Unless…

Know that you don’t know something

Socrates’ hyper-known quote “All I know is that I know nothing” fits this concept like a glove. If you want to resist JavaScript fatigue, you have to understand that there are things you don’t know —the sooner you become aware of your weaknesses, the faster you can pinpoint a problem and learn it when you need it.

Programmers who suffer from this sort of fatigue clearly know a lot about that is going on in JavaScript, so one way to avoid it is by putting some of the things you wanted to learn on hold. This may sound like a bad idea at first, but just because you know everything there is to know doesn’t mean you need it all at once. Therefore, being aware that there are some things you don’t know means you have the option to learn them at a later time.

Repeat after me: Things will continue to change

Web development is like a maze: there are so many ways you can address a problem that you will end up lost in your own code if you have too many things on your mind. As stated above, programmers can resists JavaScript fatigue if they understand when it’s time to put aside certain features.

SEE ALSO: Lessons learned from npm fiasco: How much harm can 11 JavaScript lines of code can do?

One thing is sure: web development is constantly changing. Rest assured that what’s hot today may become obsolete tomorrow or three years from now. Therefore, the sooner you accept that thing will keep changing, the further you will be from an emotional breakdown.

Everything is valuable

So you’ve chosen to spend your time on a certain framework, but you keep asking yourself if it is just a waste of time or it will eventually come in handy. In web development, there is no such thing as the right one; there’s the ‘now’ one and the ‘alright’ one but never the ‘perfect’ one. In this case, what you need to do is stop being anxious about finding the right framework and accept that everything will prove useful at a certain point. If you accept that your object of interest will come in handy, it automatically becomes a fun thing to explore.

Are you good at learning and solving problems?

Rich Hickey, the creator of Clojure, opined that “programming mastery has little to do with languages, paradigms, platforms, building blocks, open source, conferences etc. These things change all the time and are not fundamental. Knowledge acquisition skills allow you to grok them as needed. I’d take a developer (or even non-developer!) with deep knowledge acquisition and problem solving skills over a programmer with a smorgasbord of shallow experiences any day.”

In short, it is more important to know how to learn and acquire problem solving skills than to learn new frameworks because if you choose the first path, you will not have problems picking up new technology skills.

JavaScript fatigue is slowly becoming a buzzword, but instead of turning it into a real disease and using it as an excuse, why not resist it?

Gabriela Motroc
Gabriela Motroc was editor of and JAX Magazine. Before working at Software & Support Media Group, she studied International Communication Management at the Hague University of Applied Sciences.

Inline Feedbacks
View all comments