What if there are too many bugs in the team code? How to steadily improve the quality of your team's code

Recently responsible for the Android app project, due to changes in team members, the interface revision led to significant changes in code, and so on, after the release of the bug caused by the program crashes.

After the exception statistics and code, the bug focused on the NullPointerException and runtimeexception exceptions caused by null pointers, which is the most likely cause of crashes in Android projects.

The main causes of these bugs are:

1, not familiar with the project structure, lack of overall thinking;

2, writing code logic is not thorough, thinking is not comprehensive;

3, the code of the bug and the stability of the program to pay insufficient attention;

4, the project is more complex, multi-interface jump, data structure complex.

The way you review your code before each release is not guaranteed to be stable.

Code bugs are human, but they should not be found in people alone. Good architecture design and system and tool assurance to reduce code bugs at all. And in the case of team members change, to achieve a steady improvement of the team's code quality.

In practice, the following points are summed up:

1, to strengthen the importance of the issue of the degree, can not have a fluke mentality;

2, the use of mobile statistics tools (currently we are using Baidu Mobile statistics) during the operation of the bug analysis;

Note: Baidu Mobile statistics in the error report can be located to the code line of the bug, the bug processing is very convenient, during the product testing can also be fully utilized;

3, product release before the code, especially for inexperienced and did not form a good programming habits of the Novice writing code;

4, the code in the daytime error not only to modify, more important is to record into the checklist system, the ultimate formation of accumulation;

Note: This is very important, based on past experience, if it's just a matter of modification, the repetition will occur and the information can not be shared among team members.

There are no related tools available, pre-checklist can be shared with Word or Excel via SVN. Today, with 1 hours to write a simple checklist, more convenient for team members to view.

The resulting checklist can be checked against the list at the time of the code, avoiding repetitive errors, and the quality of the team's code will improve steadily as checklist accumulates.

5, the development of code specifications and strict implementation, the violation of the problem recorded in checklist;

In short, can be summed up as analysis + accumulation + sharing, no checklist accumulation, just rely on the experience of the team members accumulated, is very not reliable.

The checklist I use is also very simple, one to add a page, a list page:

To add a page:

List page:

What if there are too many bugs in the team code? How to steadily improve the quality of your team's code