The book is relatively basic, not the kind of large-scale programming, high concurrency design, etc., mainly to do some sort and some basic norms for quality programmers and some basic conventional programming designed for recruits to programmers, to develop these good qualities are very necessary; for many years has been the entry of programmers, look at the book, and then with their own situation and see if the book can reach some basic literacy is necessary.
Overall, there is some empirical summary, relatively basic, developers also have a role; for individuals, which a lot of quality, design specifications and the like have a certain understanding, but may usually not doing enough completely, so after reading, still has some of the harvest, at least with this summary of the document, to facilitate rapid follow-up review to see.
The book about the "results-oriented" covers a variety of topics concerning programming, personal responsibility, pulled photoelastic development, debugging strategies, meta programming, according to the contract design, remodeling, relentless testing, and so on. The authors believe that features programmers programmers pragmatic attitude in dealing with problems, looking for solutions, style, philosophy, they are able to think beyond the immediate problem, always try to put the issue in a broader context, try to keep the bigger picture.
The scope of this book can then project manager from beginners to experienced programmers, as a book theory and ideological bias, the book inevitably some fake big empty place, plus the author of the book written time also in 1999, a lot of methods and standards have also been placed in the book is no longer practical today. But these can not conceal its outstanding place, in this book the author has completed a decade later said that if the book is written on now, those general principles developed in 1999, as effective in 2009, assuming we today I was writing this book, and what will be different? The surface may be a bit different, we may use different programming languages and techniques give different cases, but it will not change the essence of the book, because the software is written by people, good programmer will adopt a pragmatic and practical method, the more aware of the change, to grasp the basic principles of the more important things. See their own mistakes committed before they make people believe this is a time to stand precipitation books.
As a qualified programmer to maintain sensitivity to new things, because in the IT case for technology or language Ye are to constantly updated for new things to have curiosity, to try them, there new technologies have their own or someone else had no idea of the algorithm, should try to enhance their ability, their current levels must not be satisfied, because the times are changing has been.
The book is a principle to implement DRY (Do not Repeat Yourself) principle, which is every good developer must follow the specification, the encoding process anywhere Do not repeat, repeat temporary because the time saved will give future maintenance and use huge trouble if there are duplicate code is found in violation of the principle of orthogonality or other places to look for opportunities to reconstruct immediately. So that it can have a faster, better, stronger, more elegant code.