The first chapter of the book, tells the importance of our responsibility to remind us not to keep the "broken windows" (poor design, bad decisions, bad code) do not repair. Stone soup with boiled frog story tells us the power of unity, do not overlook the little things, we should always pay attention to what is happening around, do not just confined to what they are located. This is the question I want to pay attention.
"Desire a better, always a good thing to go wrong." I have a full understanding of this sentence, in the programming, often in order to make the program close to perfect, to modify the program written, often the result of the program changed beyond recognition, even original function can not be achieved. Learn when to stop, the program is not perfect.
As a programmer, you know their computer technology, all the facts in the field of work experience and their own use of his own knowledge assets. Operate their own assets, on a regular basis for their investment assets, have more technology, seize the opportunity, do not mind learning new technology before it popular. Book presents us with some of their own money to improve the way: at least a year to learn a new language, a quarterly reading a technical book, but also non-technical reading books, classes, participate in local user groups, different test environments, keep up trend, the Internet. These to me is a great reminder that they do not love reading, even if the Internet did not have enough patience to read those scientific papers, technical papers. I wanted a lot of attention.
AC is also very important in the program development. Communication with users, understanding their needs; communicate with machines to communicate our intentions; communicate with other developers, mutual understanding of each other's ideas. To fully express their ideas, so that my audience understand their meaning.
In my opinion, these are now important for us is to constantly face.
As a programmer, we collect, organize, maintain and use of knowledge, knowledge is described in the specification we make it come alive in the operation code and used to provide the required testing process to check. Knowledge is unstable, we need to spend a lot of time spent on maintenance, re-organize and express our system of knowledge.
The second chapter tells the story of repeated problems, the general strategy for this to be addressed. Repeat divided strengthen Repeat, repeat no intention, no patience repetition, duplication among developers. Throughout the book frequently referred to the DRY principle: the system must have knowledge of every single, non-discriminatory and authoritative representation. Write orthogonal system, you can get two main benefits: increased productivity and reduced risk. Maintain orthogonality: allows you to maintain decoupled code, avoid using global data, to avoid a similar function to write.