Experiences of Internet companies on how to effectively execute Processes

Experiences of Internet companies on how to effectively execute Processes

The first six years of my career were all done in software companies. At that time, there were more processes and more strict specifications. They all had time and space to implement them. In the past few years, when Internet companies have also made corresponding implementations, they have encountered many problems in the implementation process of relatively strict standards and procedures that have been used by software companies.
There are several situations:
1. Updates are more frequent than application software. The market is changing, the customer is changing, and the demand is changing. If we do not change, we will be eliminated by the market. The customer was satisfied that the software version was updated at most once a week or even a month during the original application software development. Now, online products and services have found bugs or poor experiences, if you cannot wait for a day, the complaints will rise sharply, and the leaders and PD will always urge you to solve the problem;

2. offline testing environments are often difficult to be consistent with online production environments. In particular, cross-origin access or user verification functions that require cooperation with other websites cannot be tested online or offline;

3. The number of functions of a website can often be compared with that of a large application software. Each segment has a corresponding product manager in the optimization process. Each segment has multiple technical personnel for development, but only one package can be released at the time of release. When multiple branches are running at the same time, they need to be launched at the same time. Merging branches becomes a nightmare for developers;

4. Unable to maintain the model andCodeUnified, the Code lacks clear comments and instructions (not urgent), and the code execution performance is poor;

5. The division of labor is too small,ProgramThe staff is not clear about the deployment of the online system and the server load capacity. The code written is of poor security and scalability.

In the face of these problems, the execution process will be more chaotic, and only the transformation process can make the work more orderly. There are some solutions to these problems:
1. Control the number of requests. Although the user and Product Manager (PD) have a lot of requirements for technical personnel to solve, they do not have to solve all the problems immediately.
First, the priority of the transaction must be distinguished. In general, we are currently executing in the sequence of system exception first, bug second, and function requirement third.
The reason why system exceptions rank first is that it will cause a sharp decline in the performance of the application server, and even directly act as a machine without high traffic volumes. Therefore, it must be prioritized. The minimum requirement for tested code is that the code can be released without exceptions.
Of course, features also have a high priority, so you must sit down with the customer and product manager to discuss which are the first to solve and which are secondary. Those who have studied time management should know that priority is classified into four categories: urgent, important, not urgent, and not important.
Although it is urgent to solve the problem immediately, it is important to discuss important transactions, such as performance optimization. Although the current page opening speed is acceptable, however, without further optimization and more page functions, performance problems will become urgent transactions. In general, if we focus 90% on solving important transactions, then there will be only 10% of urgent transactions.

Second, control the number of releases. The daily press conference will make the main branch messy and make the testers exhausted. We usually release features on Tuesday and Thursday evening, so that other departments can cooperate well. Important Projects and urgent tasks can be implemented in the urgent release process, but the urgent release process is not commonly used. It can also be used to make business departments feel small and urgent.

In addition, professional SCM personnel are required to manage branches and release packages, so that testers or developers are not allowed to work part-time.

To solve the inconsistency between the online and offline environments, apart from establishing an independent test environment, we deploy the environment online on a server that users cannot access normally. The domain name is.. Net (our official domain name is. in this way, you can access and perform some tests. Of course, the problem cannot be completely solved. If you have better experience, I hope to share it with you! :)

Standardization is the foundation of team collaboration. Code without standardization will make other colleagues unable to understand your code normally or spend a lot of energy to understand your code. Busy again, a code check should be conducted once a week, the model should be supplemented, and the comments and descriptions should be supplemented.

Security and performance are important for Internet companies. The team should have colleagues dedicated to security research and execute security regulations daily. If there is a problem with standard code execution, it may take afternoon tea, but security cannot be explained and must be strictly handled. The same is true for performance. Different companies have different registrations. To allow your application server to support more than one million traffic, the code in. aspx. CS must be executed within 500 milliseconds.

The above are some hands-on experiences. The environment is a technical team of about a hundred people, and there are still many shortcomings. I hope you can learn from them.