#chat

Shushu, as a "sewer front-end engineer", I seem to know nothing except crud. It seems that I haven't become better in the past year, and I am still the same "sewer Shushu".

I saw in the group that "I will take more exams this year", and then I thought about how I haven't learned anything, read any code, or even turned on my computer in the past few days on New Year's Day. Thinking about this, I felt really sad. I couldn't help but think of the line in "Black Clover": "The thing to be ashamed of is not being weak, but being willing to be weak". Shushu, I still have this "heart energy", and I also want to get out of the sewer, and I also want to "go beyond the limit".

Positioning

First of all, we should find out what level we are at. From my understanding, it is technically divided into three levels.

Delivery layer: You can already use various APIs proficiently, write a lot of application code, handle business logic, and consider user experience. At this time you are already a qualified junior front-end engineer.

Delivery layer + infrastructure layer: Maybe the vast majority of front-end engineers are stuck in this place. This is also the level that I think is the most difficult to overcome. This level requires considering the integrity of the knowledge system, such as: framework principles/libraries, engineering, network, browser basics, performance, etc.

Front-end engineers at this level already have a relatively complete front-end puzzle system. For example: It may happen that a front-end engineer who has been writing for 3 years cannot give you a clear answer if you ask him what cjs, esm is.

And I don’t think this is an ability that you can acquire by memorizing interview questions or watching teaching videos. At most, you just collected the puzzle pieces. You cannot put the puzzle pieces together, that is, integrate them.

This means that you may know what macro tasks and micro tasks are, but you may not know that micro tasks will occupy the main thread. It seems that you already know node, then if Node+pm2+shell+fs. You may have a superficial understanding of babel and glup, but you can't do anything with them.

You 'just know', but you don't 'put together' your knowledge. What I’m talking about here is not a ‘depth issue’ (because every general direction on the front end depends on personal digging, and ‘people’s energy is limited’), but a ‘breadth connection’ (that is, you don’t have to go deep, but you must understand and have done it). At this stage, you are at the 'intermediate level'. When you 'complete the puzzle', you can 'promote to the advanced level'. At this point, you are actually more than just a front-end. You have gradually taken your steps from the front-end to the full stack.

Delivery layer + Infrastructure layer + Container layer: container, browser, AOT, JIT, protocols, standards, etc. You know them all, and you are still going particularly deep in a certain direction. You're not only out of the sewer, you're on the same page as a rat, you're already a front-end expert.

How to make a puzzle link

The only thing in the world that can be obtained without effort is age.

Let’s talk about my own thoughts. In fact, a very important point is to think independently. Everything that is beneficial to your growth is actually difficult. The benefits are directly proportional to the effort.

1. Source code reading, don’t just look at it. You have to write and output it yourself. You can’t think about the essence of the source code just by looking at it (similar to thinking about ‘what problem did he solve in the browser environment’, ‘why did he deal with it this way’, ‘what optimization did his algorithm do’ and so on). You won’t encounter the problems you will encounter in actual operation. Writing blog output is actually a ‘very good way’.

2. ‘Go to the root of the matter’. We usually encounter many problems when writing code. You get the answer through a search engine, or you change the way of writing to solve the problem. Then why can't your first thought be to dig deep? You go check issue, you go locate the problem in the source code, isn't it a better way?

3. Creativity, you can do something creative for your usual work. For example: front-end engineering efficiency improvement, component library, middleware, browser plug-in, etc.

4. Algorithm. Algorithm is actually conducive to the growth of logical thinking. It "subtly helps us grow". This is a "very long" process.

5. Standing on the shoulders of giants, the Nuggets and gitbub have many strong people. On the one hand, they read more articles, and on the other hand, their booklets are actually the integration of a certain piece of stuff. You may also need to develop an account. For example, if you compare websites, Twitter and YouTube are all technical articles.

#Business and Value

Business is the furthest shortcut for programmers

Why is it said to be the farthest shortcut? Because in fact, it is not enough to understand the business, solve the business pain points, and go deep into the business. You also need some communication and presentation skills (PPT and interpersonal skills). To put it simply: You need to understand business! You have to create value! You want to socialize! Of course, we don’t have to be so extreme (I look down on those business guys), we just need to pay attention to a balance. The above mentioned are part of personal abilities.

Business:

When I wrote this, I wrote, deleted, deleted, and wrote again. I simply didn’t like it. I wanted to be a pure technical rat, although this is not realistic.

Because the essence of "writing code" in this "general environment" is to "create value" and "create income". Your leader and your boss may not understand code, but they can still "jump on your head and scold you". Maybe your colleagues who write crappy code still get a higher salary than you. They are those people who do not understand technology or are not in-depth with technology but understand business.

Sometimes you may stay up until late at night to learn something far away from the business, which will not improve your salary or money. After all, what you do does not bring any profit. On the contrary, if you understand the business, are in-depth in the business, and can solve the business pain points, which can enhance your voice in the company, then you are definitely not far away from getting a salary increase. (I also don’t recommend staying in companies that don’t value technology).

Value:

So as a front-end, how to "show value". After all, probably most of the things done by the front-end and the back-end system, the accuracy of the data is reflected in the back-end. Personally, I think we can start from: page interactive experience, rendering speed, data volume performance issue assessment (this thing can be done by both front and back ends), engineering efficiency improvement, packaging speed. To highlight several aspects, these things can be mentioned in daily reports, year-end summaries, and review meetings, and they are also things that can "really generate benefits".

Stay passionate for the long haul

Shushu tells you, writing code is fun, and there are many interesting codes and complex functions that you have never seen or experienced, so don’t give up.

The core idea is to keep it interesting. If you don't like writing code from the beginning, it's no use changing your career as soon as possible.

Work Enthusiasm: This thing is to say that although you have to write "the same thing" for a long time, you "lose the enthusiasm for writing code", you can try the same function and do it in "different implementation methods". To put it simply: "Continuously set new challenges for yourself, put forward higher requirements", just treat "writing code as play".

Enthusiasm for learning: In fact, after entering the society, all learning needs to be done consciously. You can set some goals for yourself that are "realistic" and "not boring" and "persist in completing them every day". Hahaha, actually this is quite difficult. I suggest you start as simple as possible, because you will always encounter some times when you really don’t want to do it.

Don’t act like a fool: If the world is kind to you, then don’t act like a fool and do everything seriously. We are not saints. If you think the environment is not good, just run away, but you should think more about whether it is your own problem.

Chong: Rats, they are not such perfect creatures. Rats should go their own way. No matter what other bad rats say, no matter what the road ahead is, just move forward. The rats of today are beaten back into the sewers, and the rats of tomorrow come out of the sewers again.

Rat Rat Quotes

Shushu, I only have these things, even though they are very bad, even complete garbage. But Shushu still doesn't want to lose them, doesn't want to have nothing.