Brief introduction of web front-end development engineer

Brief introduction of web front-end development engineer

Web front-end has always occupied an important position. Especially with the rapid development of HTML5 technology in recent years, Web front-end technology has been better developed. The salary of Web front-end developers has also soared. Let's take a look at some profiles of web front-end development engineers, and welcome your reference!

The difference between Web front-end and back-end

Functional differences

First of all, we should distinguish the difference between web designers and web developers. The difference between the two is mainly manifested in: one is about the visual or aesthetic aspects of the website, which is called? Front end? ; The other is invisible coding design, called. Back end? . In short, the beautiful website interface comes from the hands of web designers, while the powerful functions are the masterpieces of web developers.

Besides the functional differences, there are many other differences between them. Downgraf, a foreign design website, made a chart to show it? Web designers and web developers (programmers) have their own problems, one has no money and the other has no time; Both of them like connotation T-shirts, one takes the font design route and the other takes the code style; Both of them have their own devices, one must bring a MacBook Pro, and the other only picks a small keyboard? In addition to the above differences, they have one thing in coMMon: they are all afraid of mm, as if they were all? House? Here comes the trouble.

technological disparity

From the technical aspect, let's take a look at what abilities front-end personnel and back-end personnel need in the actual recruitment of major enterprises.

Web front end:

1. Proficient in HTML, able to write HTML structures with reasonable semantics, clear structure and easy maintenance.

2. Proficient in CSS, able to restore visual design and compatible with mainstream browsers recognized by the industry.

3. Be familiar with JavaScript, understand the basic content of ECMAScript, and master the 1~2 js framework, such as JQuery.

4. Have a clear understanding of common browser compatibility problems and reliable solutions.

5. Have certain performance requirements, understand Yahoo's performance optimization suggestions, and effectively implement them in the project.

Web backend:

1. Proficient in jsp, servlet, java bean, JMS, EJB, Jdbc, Flex development, or very familiar with related tools, class libraries and frameworks, such as Velocity, Spring, Hibernate, iBatis, OSGI, etc., and have a deep understanding of the Web development mode.

2. Proficient in using common database systems such as oracle, sqlserver and mysql, with strong database design ability.

3. Familiar with maven project configuration management tools, tomcat, jboss and other application servers, and experience in load tuning under high concurrent processing is preferred.

4. Proficient in object-oriented analysis and design techniques, including design patterns and UML modeling.

5. Familiar with network programming, have the experience and ability to design and develop external API interfaces, and have the ability of cross-platform API specification design and API efficient call design.

To sum up, the difference between the two is that

Functionally, the front end is mainly responsible for interface design; The back end is mainly to do the function after the interface.

In image, the front end pays attention to formal beauty; The back-end pays attention to function and practicality (for this reason, I also went to Qiaobutong R&D department for a field trip and found that our front-end engineers bought two Macbook and the back-end engineers bought two keyboards. Amazing match! )

In enterprise recruitment, front-end engineers need to be proficient in JS, use JQuery skillfully, understand CSS, and skillfully use this knowledge to develop interactive effects; Back-end developers need to be able to write Java code, SQL statements, do simple database design, know Spring and iBatis, and know some design patterns.

Both front-end and back-end belong to the category of software development. So when writing your resume, you can refer to the software development engineer, which is very helpful for children's shoes!

To be an efficient Web developer, you need to do a lot of work to improve your work style and improve your labor results. However, some difficulties will inevitably be encountered in the development. So, what are the main challenges facing the front end and the back end respectively? Come and have a look with me!

Challenges faced by Web front-end development

Five challenges of front-end development

The first big challenge: compatibility

There are many kinds of browsers, such as IE, Firefox, Chrome, Opera, and many IE shell browsers, such as sogou, Maxthon, 360, plus the mobile terminal versions of these browsers. Web standards are needed. Most front-end knowledge is common to all browsers, but there are still problems left over from history. Different versions of browsers have different problems. Especially for IE system with the highest market share, although IE 9/ 10 looks quite standard, it has its own problems between previous versions, and forward compatibility is a headache. If you don't accumulate some experience, you will be at a loss in the face of intractable diseases.

The second challenge: the complexity of interaction

The interface level provided by CSS and DOM is too low, while the control provided by BOM is only the most basic and slightly complicated UI effect, which should be created by the front end itself by combining CSS and DOM. When you see a requirement, the first step in your mind is how to combine the basic parts such as CSS and DOM into the final effect. Is the final effect actually one? Create? The seemingly common components such as TabView, Treeview, Rich Editor, Color Picker, etc. are actually not available in the front end and need to be implemented by themselves.

The demand for glue in front-end languages is too strong. CSS, DOM and JS are three different technologies, and they are also the three most important basic skills that need to be mastered in the front-end knowledge system. The front-end effect is finally presented through the cooperation of CSS, DOM and JS. Without any technology, it is difficult to move, and we should always consider knowledge points in multiple directions at the same time. Front-end programming is like running three threads at the same time, and the complexity is multiplied.

The third challenge: code maintainability

The increase of complexity directly affects the maintainability of the code. The combination of CSS+DOM+JS is so powerful that the same effect can be achieved in many completely different ways, and each way will have different development difficulty, expansibility and maintainability. There are too many solutions. When you see an effect, you will first think of how to realize it with those underlying interfaces in CSS and DOM. Is this it? Create? At this time, I may have many different ways to realize it in my mind. Create? Do you want it when you're done? Compare? Weigh the advantages and disadvantages of various schemes, and after a period of time, you can choose the most suitable scheme. Of course, not all front-ends are perfectionism, so we must choose the best way, but because the front-end is GUI programming, directly facing users, it is the most direct part of product presentation and the facade. Because of this, the front end is also the most easily modified part. Repeatedly? Modify? Every programmer knows how terrible this is. If maintainability is not good, it is a nightmare. Therefore, the front end has to pay attention to maintainability, and not paying attention to maintainability is directly equal to self-abuse.

The fourth challenge: performance

The fifth challenge: personal growth

The developer's thinking is very important.

Front-end development, if there is no overall design idea, will become a fragmented program, the effect of a pile of code, the function of a beach script, and a required chip logic. Once encountered, due to the adjustment of ue, except the core data processing function, the whole front-end code has been modified. Front-end development is basically three parts: DOM operation, data processing and data interaction. If the functions of these three parts are properly allocated, the front-end code will be easy to expand and adjust.

The real front-end development challenge lies in the developer's thinking. Compatibility, layout, CSS and JS are not problems, but how to organize language logic reasonably. How to correctly abstract the modules in requirements; How to deal with it with code, express ideas and write notes clearly with code, and give subsequent maintenance personnel a readable idea. The front end changes several times as much as the back end. The front-end is not absolute, but is constantly modified according to the needs.

Challenges faced by Web back-end development

Five challenges of back-end development

The first challenge, the most important challenge of back-end development, comes from scale.

The expansion of scale, such as the expansion of visits, the expansion of file storage, the expansion of data volume and the expansion of the number of servers. A website whose front end looks exactly the same will face a lot of problems and challenges if an index is expanded tenfold. On the other hand, after the scale is expanded, the back-end system architecture will be more complicated. Originally, there was only one server, and LAMP was installed together. Then the database is separated, reverse proxy, load balancing, sub-database and sub-table, Memcache, message queue, transaction processing, CDN, NOSQL, various architectures and servers gradually evolve. The complexity of the architecture will naturally bring more problems and more challenges.

The second challenge comes from security.

Security problems emerge one after another, and it is impossible to prevent them. Need technical means and management system.

The third challenge comes from efficiency.

Whether enough processing speed can be provided, whether enough bandwidth can be provided, and whether responsiveness can be guaranteed are all external efficiencies. Whether you can use less servers, whether you can use cheaper servers, and whether you can use more energy-saving servers are all internal efficiency.

The fourth challenge comes from the change of demand.

Both the front end and the back end will face demand changes. As long as it is software development, it is a great challenge. However, when a system has been running stably and efficiently, the demand will change. After meeting the requirements, will the part without problems suddenly collapse? Once it collapses, it is a nightmare for back-end engineers.

The fifth challenge comes from dogma.

There are countless IT companies in this world. They are very open and willing to share their architecture and technology. So, for what? Broaden your horizons? For back-end engineers, the difficulty is not how to solve it, but how to choose from many solutions. Frameworks and practices are constantly emerging, as are successful cases. People use it well. Dare you use it? Is early adopter brave or conservative? This is very difficult.

Three principles of back-end development

Fault design

A considerable proportion of back-end code exists not to be correct in general, but to ensure the acceptable response of the system in special or extreme situations. There are many compromises to be made here: progressive improvement or advanced design? Horizontal expansion, business optimization, foreground or background processing? Many compromises are weighed according to the changing environment and needs, so it is easy to make mistakes.

Architecture is about abstraction.

Why abstract? Because abstract concepts are more adaptable, easier to reuse and more flexible to adapt to changes. However, abstraction is very difficult, and inappropriate abstraction is even more harmful. The terrible thing is that there is no good methodology, and most of them rely on a set of basic principles and experiences. But Web back-end development has not paid much attention to these for a long time. Many websites are extensively designed and developed, and the overlapping structure of patches naturally becomes the mainstream.

Architecture is a product.

Because architecture itself is a product, a software product contains different perspectives, the most important of which includes the perspective that users see and the software skeleton is the perspective of architecture. But the product is the product, and all these perspectives must be unified, which requires that the architecture must understand the soul of the product, and the product must understand the difficulties of the architecture, otherwise it is easy to have tragedies such as failing to achieve the function of a corner at a huge architectural cost.

;