"Front end" front end project that's the thing to do!! (Web Note)

Most people think that front-end development is a "more simple area than other modules", in which front-end engineers in their minds work:

1. Put Photoshop files, pictures or wireframe into a Web page;
2, occasionally design Photoshop files, pictures or wireframe;
3, with Javascript programming, for the Web page animation, transition effect;
4, using HTML and CSS programming, determine the content and layout of the page.

In fact, the front-end engineers are doing:

1, to achieve visual language between designers and engineers;
2, with the visual design, define a set of components representing the content, brand and function;
3. Set the bottom line for the WEB application's session, framework, requirements, visual language and specifications;
4. Define the scope of the WEB application device, browser, screen, animation;
5, the development of a quality assurance guide to ensure brand loyalty, code quality, product standards;
6. Set the appropriate line spacing, font, title, icon, fill and so on for the WEB application;
7, for the WEB application to set a variety of resolution of the image, equipment-based solid model, while maintaining the design guidelines;
8, mark the WEB application, make it semantic,seo friendly;
9, with a friendly, low power consumption, device and client-aware way to connect the API, access to information;
10. Develop client code to show smooth animation, transition, lazy loading, interaction, application workflow, most of the time to consider progressive enhancement and backward compatibility standards;
11, to ensure the security of the background connection, take cross-domain resource sharing (CORS) program considerations, to prevent cross-site scripting (XSS) and cross-station request forgery (CSRF);
12, most importantly, in spite of strict deadlines, stakeholder requirements, and equipment constraints, both now and in the future will always be "customer first".

13, a qualified front-end engineer, must be interested in visual design.

To achieve these goals, front-end engineers use a variety of tools, from visualization to programming, sometimes to take care of the market, UX, and content improvements.

Reason three: The presence of a lot of bad front-end engineers disrupts the market

This is perhaps the most obvious reason why it is difficult to recruit excellent front-end engineers. Because the front-end engineer's entry threshold is very low, JavaScript, CSS, HTML is not difficult to get started with the language, it seems as long as it takes a little time, who can learn it through online tutorials and books. Right, the front-end engineer market is being ruined by these little guys.

Bad front-end engineers do things like this:

1, misuse JavaScript library, because they actually do not have the core of JavaScript (e.g. Everything is in jQuery);
2, misuse of JavaScript plug-ins, uncontrolled reuse of other people's code, even if they do not understand the fundamental;
3, do not look at the requirements, design, nor do the comparison or evaluation, to the WEB application to add CSS framework, but only a small part of the framework;
4, that as long as the use of CSS framework, the site is responsive, or the meaning of responsive design understanding is not in place;
5, while talking about "responsive Web design", but the server-side solution technology is ignorant;
6, the use of CSS programming does not do preprocessor, naming norms, etc.;
7, ignoring performance, memory leaks (do not understand the true meaning of memory leaks), do not detect code;
8, will not use indicators to measure a product, or this indicator is designed to their own computer, browser, equipment effective;
9, ignoring 30 years of software engineering technology, behind closed doors.

You know, getting started is easy, and the basics of computers and software are important to you in JavaScript or browser programming. The Web is probably one of the most influential platforms and environments where the programs that are executed must be treated with care. A good front-end engineer not only considers Web technology and language, but also understands all the different components, systems, and concepts.

Here are the things that good front-end engineers will do in the immediate face of common tasks (this is the front end of the market):

1, DNS resolution, using a CDN, to distribute resource requests across multiple domain names;
2, understanding HTTP Headers (Expires, Cache-control, if-modified-since)
3, Steve Souders All high-performance Web page optimization rules (refer to: Performance Websites)
4, how to resolve Pagespeed, YSlow, All issues listed by Chrome Dev tools Audit, chrome dev Tools Timeline,

6, caching, prefetching, and lazy-loading techniques;
7, native JavaScript, knows when to start from scratch, when to refer to someone else's code, and to evaluate the pros and cons of doing so;
8, the latest MVC JavaScript Library knowledge and usage;
9, CSS standard knowledge and usage;
10, Knowledge of the computer science part of JavaScript (memory management, garbage collection algorithm, etc.)

In other words, if the mastery (or some of the self-proclaimed proficiency in some resumes) Html+css+javascript, the knowledge of the backend is only 60 points of qualified front end, then to become a popular, high-paying 80 excellent front end, to the business needs and, architecture design has a real use, and 100 The top-level front end, you must be able to take into account the technology and design, closer to the "front-end development-oriented full stack engineer."

Original Digest from: http://caibaojian.com/the-best-webfrontend.html

"Front end" front end project that's the thing to do!! (Web Note)