First chapter introduction
1. Develop a habit of spending time to read the high quality source code written by others. 2. When you read the source code, you have to choose from the purpose of the purpose. Clear your new programming mode, or encoding a style, or meet some needs? 3, payment details of non-functional demand in the sources of resolution, help us learn some specific implementations. 4. When you use existing source code, work with author and maintenance staff to avoid duplicate labor or failure. ! ! 5. Think about the benefits of opening source software, and look for a way to contribute to the open source software organization. 6, many times, if you want to know how "How do they do?", There is nothing more than the direct reading source code. 7. When looking for bugs, look for the source code for problems through the phenomenon of the problem, avoid blind reading source code. 8. Use the debugger to locate the position in the source code, such as: the compiler's warning or output symbol code, system calls the tracker, the database's SQL log tool, the WINDOWS system's Message SPY program. 9. You can complete a part of the system to modify the system before all the features have a good structure. 10. When you join a new feature to a system, you must do the first to find a similar function implementation, use it as your new features implement template. 11. From the function to the implementation of the code, use the keyword to track search strings and source. 12. When you modify the code and interface, focus on the problem prompting the compiler. 13. When doing code reconstruction, you should start from the running system to end with the runable system. A set of well-designed test cases help you reach your goals more effectively. 14. When you read the source code, try to find a chance to remember, you can get the biggest return from the in-depth understanding of the system architecture and consider how to enhance the level of details. 15. The reuse of the code has both temptation and confusion, so don't be too high for the reuse of the code, so as not to be more disappointed. 16. When you want to reuse, it is difficult to handle, it is difficult to understand, isolated, try to look at the code of larger particle size or other part. 17. When reviewing a software system, remember it only contains only the executable part. Also check the system's files and directory structures, create and configure steps, user interfaces, and system documents. 18, the software review as a software system study, professor, help, and receive the opportunity to receive assistance.
Chapter II Basic Programming Elements
