I have not considered my understanding of the front end. When LISTENING to Winter’s live broadcast, I mentioned a soul torture:

What do you know about the front end?

After such a question is thrown, it immediately comes to mind that HTML, CSS, JS, VUE, Webpack, etc., some messy technical points, from the technical point of view is not wrong. But it is not a system, lack of hierarchical framework, technology to serve the needs, can be competent demand development is ability. So a little summary of myself.

Visual ability

Front-end daily work is essential to restore the visual draft, referred to as the cut map. Most people get their start on the front end from Cheto. The test is the basic skills of HTML + CSS + JS, and with the rapid development of mobile devices, adaptation is also a pit. I used flexible in the previous adaptation, and now I also use VW and VH for adaptation. I rarely write mobile terminal, so I can’t explain clearly 😼 as for javascript, this language is flexible to almost no restrictions, learning it well is a prerequisite for the front end, you can play it to your heart’s content without more words!

Engineering capabilities

I got into front-end engineering in 2016 when I was working on PHP and also front-end engineering. At the beginning, I found it very interesting, and tried to rebuild all the front-end HTML of the company. I installed a Node and GLUP at will, and began to parse SASS, compress CSS, synthesize Sprite pictures for the front-end code of my project. I also tried Angular, which was the first time to try the changes brought by front-end engineering. Perhaps attracted by such a project, I quit my job at the end of that year and left Foshan to come to Shenzhen, where I began to interview for my abused life 😄 The simple engineering nowadays can be done with a scaffold, and the version distribution and packaging are all by Jenkins, and ng points to the entry file.

Docking ability

This is communication, ajax, json, HTTP, and these are the basic things needed for daily alignment, they are you communicate with the background, the basis of location problem, as to why the HTTP, in fact, I think it’s necessary, such as a 404 request, finding a service, is the clear your priority is to determine its own url is correct, Whether the server is pointing to the correct, confirm the end, and then go to the background to ask whether the service is normal deployment, rather than directly with the background said that the adjustment is not, you see, to the end is your problem, it is not a waste of others’ time and embarrassment.

The service side

Background for most of the data front-end may not touch, but since the emergence of Node, I feel that the back-end for us is no longer what scarce ability, we can also write services, mysql docking, although most will not use. We use Node more to start our scaffolding and build local servers, and because of it, the front end has become so diverse and huge that it sometimes feels impossible to learn

Writing here, the front end of my current cognition is probably like this. It is not a big problem to basically own these daily tasks. Although THERE are many fields not mentioned, I will leave some points for later writing, and I should continue to summarize it. continue~~~