1. Fatal abnormal termination is never allowed to write: User manual, manual, help, source code 3, unless you use Risk Factor Analysis (RFA), a program will cost double you think development Time --- Repeating Work 4, the code workload should not exceed 20% of the development work, should at least 30% of the project, the comment should at least 20% of the source code 7, an error message should report what happened, about this user, what is the next step, and which line of code caused this problem? It may also also pay attention to time, user name, and environment 8. Good programs will automatically send recent error messages to permanent media 9, call a routine three times? Hide it calls once? Do not hide 10, in addition to menus and error traps, routines should only need one entry and an exit 11, document code 12 with clear variable name and routine name, the database should be related 13, always use best Algorithm 14, first optimize the slowest routine, use the Profiler flags them 15. The best development language is usually 166 16, requiring customers to sign 17 on the user manual and instructions, first writing more risky Module 18, let simple maintenance becomes guiding your light 19, check each signature you wrote and spell 20, don't write any programs you can copy by a 3 * 5 card cover, know when you should do it 22, No list is perfect 23, difficulties are not what you are watching 24, the rules and rules of existence can be free from thinking
