Code SOP-2

1. You must use the full compilation method for debugging.
2. You need to use more shortcut keys when coding.
3. During the encoding process, you can use a keyboard instead of a mouse.
4. If a parameter is extracted during reconstruction, the placeholder function must be assigned a value immediately.
5. Use the Len function to determine whether the string is null.
6. To cancel the "Automatic syntax check" function in "tools-Options" of the editor, select "variable Declaration" and set the width and height of the grid to 24.
7. The call level of a function must not exceed three levels.
8. Comments must be added to more than 20 rows of the function.
9. To optimize the comparison conditions, such as short-circuit comparison.
10. All variables must declare the type.
11. Rebuild keeps moving forward, focusing on the global situation.
12. Do not pursue perfection too much.
13. Focus on the revision processCodePart.
14. After completing the phase work, you must use tools to review the code.
15. DebuggingProgram.
16. Refactoring relies on testing, especially in real environments.
17. Pay attention to the execution efficiency of SQL statements, especially the query efficiency.
18. The program must have a unified exit and entry.
19. Testing should be carried out continuously during refactoring.
20. Do not make mistakes during refactoring.
21. Rebuild should ensure that the service can be stopped at any time and submitted at any time.
22. Build an easy-to-test environment during debugging.
23. If the type of a variable is numeric, pay attention to the accuracy and range of the variable, such as integer and long integer.
24. To reconstruct a function, you must first perform a placeholder function.
25. If the if statement has only one sentence, do not use end if.
26. For time-consuming operations, the UI should provide clear instructions.
27. During the UI design, the text on the interface should be placeholder.
28. Annotations are as important as code.
29. The function name adopts the Pascal naming rule and the variable uses the hump rule.
30. If there are special conventions for function parameters, you must specify them in the annotations.