24 rules for Computer Programming

1. a fatal exception is not allowed to be aborted.
2. In this order: User Manual, manual, help,Source code.
3. Unless you use Risk Factor Analysis (PGA ),ProgramIt will double the time you think development takes.
4. The coding workload should not exceed 20% of the Development workload.
5. the test should be at least 30% of the project.
6. Annotations should at least occupy the sourceCode20%.
7. An error message should report what happened, what the user can do, what the program will do next, And what line of code will cause this problem? Pay attention to the time, user name, and environment.
8. A good program will automatically send the most recent error message to the permanent media.
9. Call a routine three times? Hide it once? Do not hide.
10. Routines precisely require only one entry and one exit exception including menus and error traps.
11. Document code with clear variable name and routine name.
12. The database should be related.
13. Always use the bestAlgorithm.
14. First, optimize the slowest routines and use profiler to mark them.
15. The best development language is usually the one with the shortest development time.
16. Customer signature is required.
17. First, write more risky modules.
18. Make simple maintenance your light.
19. Check every signature and spelling you have written.
20. Do not write any program that you can copy with a 3*5 card cover.
21. Know what should be done.
22. No list is complete.
23. The difficulty is not what you are looking.
24. Existing rules and rules can be avoided.
Abstract: Java program debugging utility Manual