This article is not technical, and there is no code to look at!

This article is not technical, and there is no code to look at!

This article is not technical, and there is no code to look at!

Misunderstood front-end development

Somewhere along the way, it became a standard thing to say about a front-end engineer:

  • Will use presents/React/Vue?
  • Master Webpack/Rollup/Gulp?
  • Used Postcss/Sass/Less?

Can these tools confirm whether a front end engineer is a good front end? My answer is: no.

The above criteria of these anomalies also caused great misdirection for many beginners:

  • Will I get a job if I learn Vue?
  • I’m new to front-end development. Should I learn React?
  • Go to the interview tomorrow and memorize the Angular API tonight.

So what makes a good front end?

Don’t let tools be the measure of your ability

What are the tools?

For developers, tools should improve your work efficiency. It is ok to use a variety of tools to improve development efficiency, but it is not ok to rely too much on tools or even without tools to develop.

For example, when Vue helps you implement data-driven pages, can’t you change the state of the page by DOM manipulation yourself? Of course not. DOM operation, as the basic knowledge of front-end development, is something that every front-end engineer should be proficient in.

Should I use this tool or not?

We all know that there are wheels flying around in the front-end industry, with a new wheel coming out every few days and a fast metabolism, and as developers we often face a conundrum: “Do I use this wheel or not?” . Faced with this problem, I generally ask myself three questions:

  • What does this thing do? It’s a simple question. Before introducing any tool, be sure to understand what it does and what its core functions are so that you can use it correctly in your project and reap the expected benefits.
  • What problem does it solve? In my opinion, the introduction of any tool should address the current development pain points, such as Vue, which helps you drive pages with data, and Babel, which helps you enjoy the syntax sugar of ES6. If introducing a tool doesn’t solve any of your development pain points, then you should think twice about whether you really need it.
  • Why do I need it? This question is a synthesis of the previous two, that any tool should be introduced with some purpose, like I wanted to use ES6 syntax in my project, so I introduced Babel, and if it doesn’t do what you want it to do, you don’t really need it.

Of course, in addition to the above points, there are a lot of details to consider, such as stability, community activity, team member acceptance, etc. As for the specific scenario should choose what kind of tools, I believe you will have a clear idea.

The paper comes to light

As is known to all programmers is a career requires the ability to learn, we need to keep learning to keep let oneself is not left behind by the innovation of technology, and knowledge acquisition channel also has a lot of, like technology blogs, articles, books, documents, etc., so the question comes, you see so many things you really will harvest more knowledge?

Are you acquiring “knowledge” or “words”?

I recommended the You Dont Know JavaScript series to him. He reads it very quickly and carefully, and almost every time he finishes reading a piece of content, he will discuss it with me and finish reading the first two volumes in about two weeks.

Before long, however, he asked me this question (roughly described) :

var count = 0

function foo (a) {
  this.count++
}
foo.count = 0

for (var i = 0; i < 5; i++) {
  foo(a)
}
Copy the code

“Why do I run a code where the outer count is 5 and foo.count is 0? Shouldn’t this point to foo?”

I was stunned at the time, because I remember in “You Dont Know JavaScript” in the part of writing this alone mentioned such an example, this man read so carefully and unexpectedly did not Know? His answer was “forget”. Then I guessed that he was just reading the book as a bedtime book, which he could pass by with a cursory reading. So my advice to him was: go back and look at each piece of demo code with your heart, and if it’s different from what you already know or what you don’t know, write it, and don’t look at anything else until you understand why it’s okay to write it that way.

Practice gives real knowledge, engage in technology is not to write a paper, do not only look at theoretical knowledge, the actual operation of the understanding than reading dry words deep much, much more. Make technical avoid by all means on paper, can not do the actual landing are useless.

How to turn acquired knowledge into productive forces?

Of course, light full of knowledge is not enough, you even convert it into actual productivity into daily work, which requires you to use knowledge “live”. As for how to really use living knowledge, I am not qualified to make a judgment, because MY own work is not good, I can only remind you here: there are only so many basic things, to use things to live, make up for the deficiency in a variety of ways is the king.

You need more than just strong coding skills

To be a good front-end engineer, it is not enough to have strong coding ability, there is also a lot of soft knowledge to master.

Learn to communicate with people

Front-end is a connecting field. In the actual business, you need to connect with UI, products, back-end and other front-end in addition to the code. Therefore, how to communicate with other roles is also a very important ability.

Do not start until your needs are clear; Find problems to solve as soon as possible; Disagree don’t refuse to communicate, find the person who can make a decision; Learn to put yourself in others’ shoes and don’t always take it for granted.

Turn “I won’t” into “I can learn”

In my view, these people are typically incompetent and refuse to learn. However, if you change “I can’t” to “I can learn”, others will have a very different view of you. No one will hate a person who is willing to make up for his or her disability.

Don’t ask “What to do”

When I was in junior high school, my head teacher said, “Don’t panic if there is a problem, find a solution and the problem will not be a problem.”

When I was in college, my mentor said, “Don’t be the one asking the questions, be the one giving the answers.”

Think about it for a moment. If you are your boss and two subordinates are reporting to you, one asks what to do after describing the situation, while the other describes the situation and comes up with several ideas for you to decide which one you prefer.

conclusion

Having said so much, I just want you to:

  • In terms of technology, we should pay more attention to a solid foundation and take the application of tools as a way to improve efficiency.
  • Besides technology, we should pay more attention to the cultivation of emotional intelligence, problem solving, independent thinking and independent learning ability.
  • Of course, there is the most important point is: must have a good body, more exercise less stay up late, blacksmith also need their own hard ah.

PS: We are also looking for physical and mental health, correct three views, ability, emotional intelligence, high small partners, interested students can contact me alone, no limit of years, no limit of education, no limit of experience, only ability, meow!