Is front-end technology important in terms of depth or breadth?

foreword

A few days ago, I discussed with my friends "Which is more important, the breadth of technology or the depth of technology", and then I thought about my front-end journey like a roller coaster.

Why do you have this question?

I still remember two years ago, or even a year ago, when you wanted to find a good job, you had to do at least a few things:

  • Proficiency in the use of a certain framework

  • Read and explore in depth how the framework works

  • Proficient in various JavaScript stereotypes

At least you have to do the above things well before you can find a better job, but in today’s situation, looking at the various recruitment requirements, it’s scary, and people can’t help asking: only the above , Can you still find a good job?

thinking about self

I still remember two years ago, when I was a very pure front-end programmer, what I thought at that time was:

  • I am the front end, I only do front end things

  • The company must have a clear division of labor. People in what positions do what positions, and I will not be asked to do back-end work.

  • It is impossible to learn things other than the front end, it will only affect me to learn the front end more deeply

I remember that at that time I also wrote a special article to diss those who encouraged the front-end to learn the back-end. At that time, it was indeed "carefree" and only needed to think about the front-end things.

Later, I entered a company and went through three processes:

  • Forced to change from a "pure front-end" to a "full engineer"

  • Then to fully adapt to being a "full engineer"

  • Then to learn something from the identity of "full engineer"

This experience made me understand a lot. Only then did I know why those front-end bosses can become front-end bosses, because they know a lot and can think about the products they make from multiple angles, not just from The angle of the front end.

Technical depth or technical breadth?

After talking about my experience and opinions over the years, let's go back to the topic and talk about technical depth and technical breadth. I personally think that in terms of the current front-end situation, the breadth of technology is undoubtedly more important. You can go to Boss to see it. A slightly better company has a lot of requirements for the front-end, such as:

  • Not only web pages, but also apps

  • Not only the front end, but also the back end

  • Not only the front end, but also some operation and maintenance/operating system

  • Not only the front end, but also product thinking

In fact, if you think about it differently, this is also normal. If you are a recruiter for a company and there are two applicants with the same expected salary, one will have more skills and the other will have less skills. Don’t you think the former is more cost-effective? ? After all, most companies are recruiting for immediate combat capabilities, and you need to be plug-and-play when recruiting you. There is a high probability that more people will have better learning ability or richer project experience, so they will definitely integrate into the team and develop projects faster~

However, it is not to say that technical depth is not important. The two things of technical depth and technical breadth have never been single-choice questions, but multiple-choice questions. If you achieve technical breadth + technical depth, then you don't have to worry about finding a job at all~

​Is the saying "the front end is dead" popular now?

The saying "the front end is dead" is popular on the forums now, and the more it spreads, the more people become anxious. In fact, I don't agree with this statement. I think it's just that the current front-end market is oversupplied. Many people's current strength can no longer keep up with the requirements of the market, so the only way is to improve yourself~

 Here I highly recommend everyone to try the JNPF rapid development platform. This platform relies on the principle of low-code development technology, so it can improve the pain points of long traditional development delivery cycle, difficult secondary development, and high technical threshold. In addition, a wealth of solutions and functional modules are provided in the background of JNPF. Most of the application construction is realized by dragging and dropping controls, which is simple and easy to use. The OA system is built and used in JNPF, and the work response speed is faster.

 The latest open source project recommendation: https://www.yinmaisoft.com/?from=csdn

Front-end technologies are constantly being updated and iterated, and new technologies and frameworks emerge in an endless stream. The big guys all said that they want to pursue high reuse, high cohesion, low coupling, and easy expansion. Seeing that the community has begun to discuss low-code, everyone seems to be quite excited.

  • Not limited to framework

  • Not limited to the front end

  • not limited to development

In fact, if you think about these points carefully, isn't it the embodiment of the breadth of technology? I don't want to force you to take papers and study crazily. I just give you advice as a person who has experienced multiple front-end processes. I hope you can find a learning method that suits you, so as to improve yourself!

Guess you like

Origin blog.csdn.net/yinmaisoft/article/details/131394220