1 think clearly, write clearly, speak clearly, is really clear.
2 spend more time to communicate clearly the needs, in order to grasp the right direction.
3 The cost of fixing a requirement error is dozens of times times the code error.
4 The biggest bad habit of programmers is: rush to write code.
5 The shortest way to improve the efficiency of development: do it once, not rework it.
6 before writing code three things:
To figure out what to do;
Speak clearly how to do;
Want to know how to measure.
7 Professional Programmer design Program, amateur programmer debugging Program;
8 Copy paste mode of operation, the most easy to import bugs, the most difficult to debug.
9 Repeating code is the source of all evil.
10 small functions, small methods, with the function of naming, you can eliminate comments.
11 do a little, testing a little, test-driven development, rework the least, rework the most easily;
The complexity of 121 methods should be less than 10, otherwise it is difficult to debug it.
13 refactoring code at any time, no legacy spam!
14 Eliminate the warning and error of static checks.
15 of professional programmers are to prevent bugs, amateur programmers are to modify the bug;
16 often summarize their lessons and write them down. Rolled up together.
17 Any complex problem can be simplified by two simplified means:
Split by Time series, split by the whole part, 18 daily build, daily confirmation, early detection of errors, rework as early as possible.