Shulou(Shulou.com)06/01 Report--

I don't know when someone suddenly mentioned the front-end engineering. at first, I thought it was a profound word deliberately mentioned by some god, specially to scare people.

Then I crazily searched for a lot of information. in nearly 20 related materials, each article was miraculously written and full of egotism, but when I read it, it always felt wrong-- that is, everyone used their own set of relatively standardized development routines as front-end engineering, and front-end engineering turned into front-end optimization, and people saw, "Yes, this is more standardized, and the optimization is good." Barabara ", but also feel that engineering should not be just these, like the lack of something, let people see in the clouds, seem to understand. Although this kind of article is not misleading, it is secretive and demonizes the front-end engineering.

As usual, I asked several front-end friends, but the answer is the same. Front-end engineering is standardization, construction automation, test automation, as well as modularization and componentization to improve the efficiency and quality of collaborative development. This does not satisfy me, and I feel that the most critical point has not been pointed out.

So after I understood this, I felt that I should first put aside what they said and settle down to think about this topic.

What is the front-end engineering?

Front-end engineering is a kind of thought! In a moment, I had such an answer in my head. First of all, the front-end engineering should be an idea, not a specific engineering plan. Most of the previous articles and people are talking about the plan, and it is too frivolous to explain an idea with a plan. Just like modularization, using webpack/broswerify, or requirejs/seajs,AMD/CMD/CommonJS is modularization, which can't be explained in this way. Even the official website of webpack said, webpack is a module bundler, we can realize the idea of modularization without even going to the tools mentioned above. To cite another simple example, that is, the realization of socialist modernization, first of all, it should be a guiding ideology, and those five-year plans are concrete plans, which are specific principles for achieving socialist modernization. the policy has a lot of targeted solutions, but they all go around the guiding ideology.

So! Under the guidance of this thought, we can work out a plan that is suitable for our own project. (don't copy the plan directly, at least until you understand the idea.)

So, what is front-end engineering?

Front-end development, first of all, software development, then front-end engineering, should be part of software engineering.

The concept of software engineering (software engineering) studies and applies how to develop and maintain software in a systematic, standardized and quantifiable process method, and how to combine time-tested and correct management techniques with the best technical methods available at present. "(Wikipedia)

It is very important to analyze this sentence carefully.

How to understand this system. According to the concept of the system, the system is a combination of several interrelated, interactive and interdependent elements, which has a certain structure and function, and is an organic whole in a certain environment. What we have to do must be interrelated, there will not be a single element is out of the matter, and is an orderly arrangement, the formation of a holistic whole. The emphasis is on relevance and integrity. In terms of software life cycle, definition and planning, requirements analysis, software design, program coding, software testing, operation and maintenance, each step is closely related, and then form a complete process. To put it beside the point, the commonly used life cycle model, in modern software products, pays attention to fast iteration, that is, iterative model.

Standardization. Specification is literally easy to understand, but the question is, what do we need to standardize? In fact, every step in the life cycle of software requires normative standards. As a software engineer, I mostly pay attention to the specification of program coding, and I don't know much about the rest of the life cycle. From development environment (version control tools, IDE, database, etc.), programming style (code format, naming convention) to programming experience, automated construction and testing. These should have standards, of course, the depth of the specification is also worth considering, because too many specific standards are sometimes difficult to remember and implement, so sometimes it is advocated that the agreement is greater than the configuration.

A quantitative process method. Like the systematicness and standardization mentioned above, quantificationally describes this process approach (development process). But quantitative this is nothing to say, you can specify the quantity (this explanation makes me blush).

Correct management techniques. Management is people, things, things, in terms of people, is the method of how to work as a team; in terms of practice, it is the initial process of coordinating this matter; in terms of things, it is the control of something concrete, such as the version control of the code.

The best technical method. In terms of programming development, it can be simply understood as what language, tool, framework / library to use is best applicable to your project. (there is no best technical method, only the most suitable)

Therefore, from the above methodology, the purpose of software engineering is to improve efficiency and ensure quality.

So, if you understand front-end engineering from the concept of software engineering, what can front-end engineering be interpreted as?

Meituan Dianping technical team has an article "front-end engineering development solution app-proto" summed up particularly well. According to the specific business characteristics, the front-end development process, technology, tools, experience and other standardization, standardization is the front-end engineering. Savor the concept carefully and you will find that it corresponds to the concept of software engineering one by one. Some people may say, why is there no componentization, modularization and automation? I think componentization and modularization should be classified into programming experience, and it is not important enough to emphasize it. And automation can indeed be added (after all, it is a killer to improve efficiency). What I would like to praise in particular here is that the title of the article indicates that it is a front-end engineering solution and does not mislead people.

So what is front-end engineering?

The front-end engineering is to standardize, standardize and automate the front-end development process, technology, tools, experience, etc. At this point, front-end engineering is no longer an ambiguous concept. Under this concept, how to instruct your own project development, I think software engineers can do this:

Choose the appropriate framework and library first because it will affect your tool selection and code specifications.

Select tools, including development tools, version control tools, build tools, testing tools, and so on.

Develop code specifications, unified programming style, with tools for verification.

Choose the development mode (similar to the modularization and modularization mentioned earlier), but generally this is combined with the framework.

Use tools to automate the development process.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.