Individual programming, not team
1 Avoid infinite loops and avoid adding heavy tasks to loops, such as loop queries
2 Make analysis records and add records where needed. When debugging is not possible or the debugging is unclear, it is easy to view
3 Name and use your own rules
4 The distribution of the files is simple and clear, and the level is too deep, which is not conducive to understanding
5 important places to write notes
6 If you have a good library, don't implement it yourself
7 The code is indented, line breaks are neat, easy to read and write
8 Use memory reasonably, and destroy the place where it should be destroyed
9 Design before development. When it needs to be improved, it is convenient to think. For complex needs
10 Reasonable use of dynamic variables, suitable for flexible scenarios, not suitable for efficiency-first scenarios
11 In process-oriented design, avoid using methods or functions that cause unpredictability to the process, such as sending emails, remote retrieval (curl), etc., which can be solved by asynchronous methods.
12 Make a backup, use svn or git for code, seafile for documentation, and rsync for formal data
13 Since there are many types of code languages, code mixing occurs in most cases. It is best not to mix code when writing with one code.