This is a series of MDH weekly articles. You can subscribe by searching “Yunqian” on wechat.
1. I usually spend 1-2 hours a day getting front-end information, but there is so much information, such as database releases, industry news, Twitter lists, RSS feeds, public accounts, newsletters, group chats, etc. Attention is being collected everywhere, and our time is limited.
Attention is limited, choice is very important, give up is also very important. Every choice has an opportunity cost, and if you spend an hour watching gossip of limited value, you’re giving up better information. We need to decide what to watch and what not to watch all the time. Input determines output.
3. First look at how to identify information and knowledge. To give a few examples, how SWC authors add next.js is information, how SWC accesses next.js is knowledge; Umi release 3.5 contains MFSU speed up is information, MFSU speed up principle is knowledge. Information is so addictive that I often go through an hour of scrolling and then regret it because I didn’t learn anything. So focus more on knowledge and less on information.
4, someone said “I learn so much front end every day, but why still write bad web page.” It depends on the ratio of information to knowledge. If the ratio is 8:2, 9:1, 10:0, what is the use of looking at more, and that little bit of knowledge ratio may still be “collecting is learning”. I’ve been at 5:5 or 4:6 for a long time, and I’m trying to get to 2:8.
5, put aside the information, there are so many front-end knowledge points, which is important? What are your priorities? Which ones are useless?
6. What is dead knowledge, such as who is the author of JavaScript, how many Chinese characters are vertically centered, what is the relationship between Java and JavaScript, Umi is pronounced five meters or Umi, MDH is Ma Daha or Ma Dehua, The difference between Event listeners and Event handlers and so on, they are not useless, they are not useful, like the human cecum.
7, work related knowledge is a priority to learn, learn to use, not optics is too easy to forget, I have deep experience. For example, at the present stage, I mainly focus on framework, construction tools, engineering, data flow, routing, etc., followed by performance, internationalization, permission management, buried point statistics, Serverless, SSR, etc., less attention to graphics, low code, animation, Node framework, container, K8S, editor, etc. These are far from the job.
8. If the time line is prolonged, basic and rational knowledge will be more important, and they have stronger fertility. Algorithms, design specifications, ECMAScript specifications, HTTP principles, browser rendering mechanisms, modular systems, the underlying principles of Vue and React, etc. No matter how fast the front wheels are built, this knowledge is hard to expire, and it’s consistent and thought-provoking.
9. The same logic applies to the selection of articles, libraries, and technical directions. For example, when judging articles, I often ask myself “Will this article still be valuable in three or five years or more?”
10, there is “as far as possible to choose difficult knowledge”, the simpler the value of the smaller. You can learn something immediately, and it’s not very valuable. For example, writing a sleep function by hand is more valuable than writing a React function by hand. How to do if you don’t understand the difficult knowledge? Brave scalp read, read repeatedly, perseverance is not much, so it is more valuable.
Photo: [email protected]