How to overcome the fatigue of JavaScript framework?

"Editor's note" Tero Parviainen has a Build Your Own AngularJS, has two times to organize Clojure CUP competition, on Twitter has nearly 2000 followers. In this article, Tero elaborated on the emergence of JavaScript framework in the present, a lot of developers on the choice of the framework of the various puzzles, if you have similar confusion, may wish to read.

The following are the translations:

The JavaScript community is plagued by "frame fatigue". Looking at a lot of new frameworks, technologies and ideas that have sprung up in the near term, it's exciting to find it hard to catch up with the pace of technology updates.

Since it is difficult to catch up, you have to choose the areas of focus, and that is precisely because of this anxiety. So, are you concentrating on the "Right thing"? Is the framework you are learning the most suitable for you, and perhaps better than it? What will happen next month to make your choice look outdated?

Here are some personal summaries to combat this feeling of exhaustion and anxiety.

1. Learn to appreciate the unknown in the known

In fact, if you encounter this problem, you already know what's happening around JavaScript. All you think you should learn is something you know, and they are the unknowns in your field of knowledge. Here, you have to understand that the "known unknown" will continue to expand indefinitely. In fact, the opposite is true: not only does it mean that new things are going on, it means that every time you learn something, you learn about it-things that you don't already know about.

For example, when reading Cycle.js, it was found that little was known about reactive programming. Learning React brings the way to contact React Native, graghql, and Redux, and so endlessly repeated. One thing can always lead to another thing.

Instead of being disturbed by a series of known unknowns, learn to accept the situation. When you are aware of a lack of knowledge, you can choose to follow it. Knowing that it exists and presumably knows what it is, it means that you can decide at some point, if possible, to take the time to learn this knowledge. We are always in the choice, inclined to resist this choice but because there is still so much knowledge and feel guilty. This entanglement is meaningless, and making choices is better than ignoring all the things you can learn.

This unknown--what you do not know--cannot be used as an alternative to practical knowledge and skills, but it is by no means useless.

2. Accept that things are always changing

There is no doubt that WEB development is constantly evolving-better solutions are shared, or device performance is enhanced, and so on.

No matter what the cutting-edge technology of JavaScript is now, I'm sure this "frontier" will never last for 3 years. Most of them will be long forgotten and some will remain, but innovation may revolve around something we can't even imagine.

For example, the Angulai 1.x is still strong and will hold for several years, but there is no innovation around it. This will also end up in React or other technology that seems to be novel today.

We may not want this to happen, but it is an unavoidable reality, and you can only choose to accept that things continue to change or stay behind the inflection point of cutting edge technology. Any kind of choice is effective, but it also has to pay the cost. In any case, change is ongoing, and trying to stop it often has little effect.

3. Understand that everything is valuable

No matter what frame or technology you choose to use for your time, the payoff will ultimately be rewarded, even if it's not the right one. Everything you learn is helping to build a network of neurons in your brain that will help you build a connection that makes it easier to follow up on other things, and understanding a knowledge that allows you to compare and contrast with other knowledge. Therefore, learning is always useful, no matter what you learn.

It also means being anxious to find the right framework or technology to learn and not be as important as you think. Not only because the so-called correct frameworks or techniques are difficult to determine, but in many cases they do not exist at the outset. On the contrary, finding useful knowledge is clearly simpler and ubiquitous. You might be able to learn something that looks interesting, even if it's not exactly the right thing to do.

For example, I spent years learning a variety of ruby technologies and using Ruby and Rails as apps, and today I don't have them, and I'm not even sure if I'll use them later. So does that mean that I spent that time with nothing? I don't think so. Those techniques were not only useful at the time, but all the things that were learned at that time formed my current coding style. I very much hope that this will finally happen to the tools I am learning now.

So, how do you get rid of the anxiety that arises from finding the right frame? Here you may want to look for knowledge that may not be so useful at this time-find an interesting computer science paper and explore it, or spend time on techniques that do not apply directly to what you do. The benefits you get from these places may not be so obvious, but they are real and appear in a casual place. It's also exciting to get out of the tough frame options for the moment.

4. Learn to learn

Another effective way is to return to the source, only to spend time on learning to learn. Why not practice the process of solving the problem itself, or study the technology as if it were a deliberate practice. Similar behavior will help you understand what a career really can bring.

This is Rich Hickey's view on this:

You need to carefully identify the nature of the matter. Proficiency in programming is not a language, paradigm, platform, building blocks, open source, conferences, etc. These are the basic knowledge that changes over time, and the ability to learn knowledge can make you use it on demand. I prefer programmers who have good learning skills and problem-solving skills, rather than a programmer who only learns from superficial experience at any time.

Just as learning a new framework is valuable, learning to learn can obviously get a bigger payoff. Being good at learning and solving problems will make you less troublesome, no matter what new technology you will need next.

Original link: Overcoming JavaScript Framework Fatigue

This article is compiled and collated by OneAPM engineers. OneAPM is an emerging leader in application performance management, enabling enterprise users and developers to easily implement slow program code and real-time crawling of SQL statements. To read more technical articles, please visit the OneAPM official blog.

How can I overcome the fatigue of JavaScript framework?