45 Habits of efficient programmers--agile debugging (Ⅶ)

True master only know how to mend!!

Record the problem resolution log:

When the same or similar problems occur later, it can be quickly found and resolved;

To share the logs with the team, not just by one person;

Second, the warning is error:

Ignore the warning information to continue to develop the code, no doubt the program loaded with a time bomb, it is likely to explode at the worst moment and difficult to solve;

　　Some warnings can be a serious mistake!

Third, the question conquer:

Do not try to understand all the details of the system immediately, in order to carefully debug, you have to separate the problematic modules and other code base;

It is useful to locate the problem in two-point way!

Iv. Report All exceptions:

The reported exception should have practical meaning in the context of the Code;

To propagate exceptions that cannot be handled;

V. To provide useful error messages:

Provide a more easy way to find the wrong details, and don't let users get confused;

Distinguish between error-type program defects, environmental issues, and user errors;

Do not disclose security information, personal information, trade secrets or other sensitive information;

　　

45 Habits of efficient programmers--agile debugging (Ⅶ)