"Pragmatic Programmer" the sixth book review

43 merciless test
       test is to protect the quality of the code. So the more carefully, thoroughly tested, the more robust help system, irresponsible programmer or testing, data can always hold to the normal operation of the test. Conditional tests still need full-time, qualified test, but not the kind of code even see the little girl just graduated do not understand.
44 are all written
        documentation and comments. Notes from that aspect is also decent, but in some cases will still ignore the comment while the latter make up, it needs to be corrected. As for the case of the document actually need to work hard, this will significantly more "professional", to better record the code.
45 great expectations
        meet customer expectations, the software is the real success. This is, in fact, also involves the "evil" demand. Has just gone through a finish of tracer bullets were shot customers do. In fact, all of this, if from the beginning has been customer expectations, it would not be so bad. And the fact is that customer expectations, customer demand is not available. Although this is not the typical good software engineering, but at least we now know what is our customers' expectations.
46 extreme arrogance and
        a very cool name, is not it? In fact, only refers to a small thing, leave your footprints in your code above. This, the first time the company has developed a habit, and retained to the present. Although there is no sort of requirement, but I will continue to do it, because for himself, for his teammates, good habits are very important, when people find a problem, they can immediately came over and asked me: Hey, why is there this problem. He can save his time, I can once again have the opportunity to increase their experience (see my previous experience). And left their mark, but also left a sense of responsibility, irresponsible people, it can immediately be found.