What should the front end of a small company do?

Objective

Recent work life compared to the drifting, from Shanghai to Chengdu, this is a family as a unit of the major decision, leaving the first-tier city for career and technology forefront is a certain problem, but for the price considerations (mainly can not afford to buy a house) and life comfort, return Rong seems to be a better choice, Besides, the Internet in Chengdu is also OK.

With the ability to improve, responsible for the type of work will gradually increase, the direction of consideration will be different, this time there will be too many separate points of knowledge become a hindrance, the work encountered in the problem is too "big", summed up laborious, or too "small", not suitable for the individual collation, This phenomenon instead caused a period of time of the blog blank period, in general, and began to lazy, thinking and began to slack, people began to want to stay in the comfort zone.

Because began to lazy, so did not learn new knowledge, natural out of the new text, because began to lazy do not want to work in-depth study of the problems, digging into the nature of the new text.

So people still have to constantly flogging themselves ah, can not let themselves into the "blind busy" situation, the effective use of time, to go farther!!!

Now I am in a small company to do the front end, because the company and the position of the change, for small companies how to do the front-end have some experience, take out with you to do a share, hope to be in the front end of small companies have certain usefulness, also flogging their own re-study summary.

What is a good front-end team? What does the team lack at the beginning

In the company, the higher the level of business concern is higher, but not too concerned about personal growth, so the evaluation of a leader is team-based, team members stronger than he should be, for individuals, to pay more attention to their own ability to grow, and then ability to match their position, or even beyond their own positions, Such a team, the combat effectiveness is relatively strong.

Supervisors (including front-end supervisors) Set goals that must be quantifiable, such as what you do with a business, how many KPIs, then technology needs to consider how to achieve, refine to research and even the front-end level, the so-called technical KPI.

For example, this year H5 station wants to reach 100 million of the traffic, then this is the business objectives, need to digest the various business teams, can be:

①seo optimization

②sem optimization

③ Marketing Advertising

......

Of course, can only solve some of the problems, specific to the front-end, we may have to start from the page conversion rate, the establishment of order funnel model, do performance optimization, to do interactive optimization, each specific level needs to transform the target.

These are directly quantifiable things, because the current business has reached a bottleneck, or the company has reached a bottleneck, the business needs to do not stop trying, corresponding to the technology is to need you fast iteration, low-cost iteration, continuous fault-tolerant trial and error.

There are a number of questions to be raised at this time:

The first is that your team will work overtime to achieve the company's goals and personal KPIs under similar high pressure.

The second is your team in this round of high pressure after the struggle to leave anything?

According to previous experience, no team can withstand the pressure of high pressure overtime indefinitely.

With the previous experience of Ctrip wireless high-pressure iterations, even so excellent team in fact to the late is also exhausted, tired when easy to make mistakes, Prince regret, surplus can not be long.

The third is how to help new people quickly into the team, how to let 1+1=2.

We all know that a good project is not a heap of people can be piled up, how to make a project can be broken down into the hands of the individual, how to let the mixed colleagues can better collaboration, this is what we need to consider.

To solve these problems is to rely on the usual accumulation, the concrete embodiment of the front-end is:

1 in a nonstop iteration, your business process is not optimal (product to design to front end to final on-line process) 2 in non-stop iteration, whether to precipitate out the public service and the tool service

What's a good front end?

First of all, a good front end is willing to work overtime, at the same time, a good front end will find ways to let the team less overtime.

Communicate with some friends, a lot of good ideas, improve the efficiency of ideas are a few people after the discussion in private night, and then repeated practice for production.

Business KPIs are generally not too difficult for a strong friend, so expect more from them:

Have a strong sense of understanding the current project performance defects, the development of inefficient reasons, and will find ways to deal with

Many teams in the rapid iteration will start "outstanding", time is not willing to also, the existence of the problem need to find a way to solve, team members are to see the problem, no one said, no one do is because know that is the pit, if you can solve, one to two times can improve their position in the team.

Good front end should have good architecture design ability

First, a good front-end can be clearly organized to describe their own technical solutions, and let people understand!

Then the architecture can meet the long-term demand development, even if the business channel expands 10 times times, the user quantity increases 100 times times, also does not have the fundamental change.

A good front end should have good communication skills.

Internal, good front-end needs to understand the character and ability of team members, make appropriate task allocation decomposition, external, need to seize business also can not generate conflicts of interest, such people are the main thrust of the project.

What should the front end of a small company do?

Not all small companies are like this, but the front end of the small company I've seen is flapping business, and it's a vicious cycle, the first time doing business:

Work overtime-business end Easy week-overtime drive iteration-business end Easy week-overtime new business-business end easy ...

Occasionally you will ask these friends why do not accumulate, get the answer is basically consistent, busy Ah! They are really busy when they are busy, but the second time if it is still so busy, there is a problem, the third time is the team is not healthy, a good practice is:

① complete before and after the separation, this step can not be done, back also do not have to do ② to form a few sets of UI library ③ according to business form, the formation of public services ④ front end repetitive work tool ⑤ form an optimization system ⑥ form a statistical system ⑦ set up a page conversion funnel model ⑧ do abtesting program ...

First of all, regardless of what considerations, must be done before and after the separation, if there are SEO needs, then follow-up to promote the Nodejs program, after all, now do not give money to row in front or difficult, seo basically meaningless.

In fact, small companies have a lot of pits can occupy, this will help you build a team prestige, below I give a few details point to say.

UI Library

How much of the UI library is formed and how much of the UI library will determine the amount of rework you have for subsequent projects is a few points to note:

Whether ①ui can be reused

②ui whether it can be customized

For example, let a lot of friends to do this time selector, made to really is the time selector, if let him replace the city selector, it is completely dumbfounded:

Whether ③ui can be split, can be aggregated

Or in the case of the UI above, this component is actually an aggregation component, consisting of a select component and a pop-up layer component, and your UI is not detachable is a great consideration for evaluating his quality.

......

Public service

A public service can be said to be a larger "UI component", but he is business-related, and the UI is generally not decoupled from the business, with the date selector above, whether it's a date or a region that is possible, and should not request a service, he is a pure UI component.

And the public service is impure is certain business-related, mobile-side more common public services are:

Passport

Include login registration, profile management, and even include some certification related, company account related operations, login registration is a variety of activities, all kinds of business channels are likely to use the business, this thing must be served, but many small companies did not do.

Because of the public characteristics, page design is best neutral point, several of the commonly used pages, such as login needs to include the following design :

① styles can be customized (pop-up layers, standalone pages, etc.)

② fallback can be customized, in fact, all the public service fallback button is required to customize, login successfully to which URL login failed to go to which URL, click the browser to go back to which URL is agreed, less one is not a public service

③ Single Sign-on, in fact, the initial use of no single sign-on, and even people are not cross-domain, so the subsequent need to support the

There are also many public services like passport, such as:

① wallet service, including user payment order related management

② city list, which takes into account how the parameters are passed

③ Feedback System

④ Company Introduction

In addition to the public page service for the C-terminal, there will also be a statistical platform for the B-terminal related.

End-of-tool

Static resource Processing

Evaluating whether a front-end team is a good mature judge is more of a team tool, a simple example is:

① how your front-end static resources are organized and packaged

② how your front-end static resources are resolved (the better scenario is MD5)

The above two points can be easily done using the Grunt/gulp class of build tools, and if there is a common framework file you will need to introduce the concept of a seed file

Cross-domain issues

In addition, all front-end teams will encounter cross-domain issues, especially after the separation, the server side only provides API interface, the front-end code can run anywhere, then what do you do this time?

① using Fiddler&charles as an agent

② providing a test server

③ supports JSONP cross-domain

④ supports cors across domains

So these programs, which is best for the team, which is the lowest cost (generally the agent), we need to consider

Tips: I used fiddler before, now for Mac use Charles, two tools very good, regular piece of processing very well, recommended to use

Mobile-side adaptation

From the back end to the front-end students generally have some natural advantages in business logic, but often in the CSS a weaker, how to introduce rem in the absence of developers, how to use less than the existing mechanism, how to deal with the pollution of the CSS in a single page application, this is the framework of the bottom of the need to consider.

Modular & Component Development

After the scale of the team, how to use the modular development to deal with the problem of collaboration, how to use the component programming thinking to develop complexity, which needs to be applied to the project practice, and the path is replicable, after the increase of business code complexity;

Some optimization tools, also need to be instrumental, framing, so that developers do not feel.

Front-end collaboration

Front-end and server-side, development speed may not be synchronous, in fact, many times are not synchronous, in the case of the interface format has been agreed, the interface has not been written well, but the front-end can still write the interaction, the team is how to write this fake data, this aspect of implementation will greatly improve work efficiency.

Order Descent Analysis

If in a certain period of time, the total station of traffic or the total station order volume down, how do you track the cause of this decline, how to avoid the next occurrence of similar phenomenon, this time data statistics will avoid us become blind, so we have to set up a statistical platform, conversion rate model as soon as possible.

Quickly iterate to optimize the product through iterations, but if each iteration is completely subversive of the previous design, many times the company is in place, and every step you need to know clearly the previous version where the problem, to optimize for the problem, rather than frequent revision.

After this revision, how do you know this optimization is better than the last time, and not other factors caused, abtesting plan should be every mature team must, continuous optimization these are based on effective data monitoring and feedback mechanism, we can not finish the website into blind.

Conclusion

Because I have not written a blog for a long time, and because recently came to the small team, there are some ideas in the form of hydrology sent to discuss with you, I hope to be useful to you.

Admittedly, for a front-end, to promote the above work is still a bit difficult, but not impossible, the front-end of their positioning to change, from the front-end engineers to software engineers.

I often hear a lot of front-end myself questioning myself, or just inflated to feel that my team has nothing to do, then this time can be considered:

is the automation and security of your team in place, and is there really no room for increase in efficiency?

The attention of the front-end needs you and I work together, in large companies to do front-end difficult, in small companies to do the front-end more difficult, you and I share!

What should the front end of a small company do?