When I started reading, I didn't intend to finish reading it. Because the book is too thick, time is not enough, when I read the preface, I found that can be skipped, so I read from a chapter that fits my identity--11 Chapter
The power of variable names:
Just started to learn C language, what do not understand, so the details of the code is not very good, write code to write the variable name always follow the feeling, because it is the job form, so what variable names do not matter, the next time will not see the code once written. However, as my learning goes deeper, the code is getting longer (and certainly not too long), and the meaning of memory variables is difficult, but because of the young, memory is good, so remember to live on the past. With the passage of time, one day in the new project to find a small part of it is very difficult, has spent a lot of time to complete, so in order to save time to reread their own written code recalled the idea of the time. When I "read" The code I wrote, a few comments, the variable name is Ijk, then I, very regret why did not write the details.
So, variable names are just as important as annotations, and even more important, you don't need to be able to read the contents of the comments directly, saving time.
Software components:
A large project is not a overnight, or a person can accomplish a task, like building a house, a person is a day to complete that is a kennel. High-level architectural complex, need to design, construction and many other aspects of co-operation, then we need to plan for the house. The production of software is the same, want to complete good software works, need to build optimization software. Of course, building a house you will not even make a table chair, so when writing software, the library functions, the use of various components and their own or other people's code reuse and so can be used as raw materials. Careful planning does not mean that you need to make sure that you have made enough plans and that you will not be able to cause major problems later because of the lack of planning.
Code Daquan reading notes (i)