Summaries and Customer Reviews are supplied by Amazon.com

Average Customer Rating:

Code Complete Review	Customer Rating:
the product was good,the delivery was on time. The book was in good condition

good book	Customer Rating:
I bought this because it was highly recommended as a must have for the software engineer. I browsed through it and I'm not sorry I bought it. It has some good stuff.

Best of the Best	Customer Rating:
Besides agreeing with the other reviews all I can say is that this text has made me a better programmer. Truly.

An Important Read	Customer Rating:
Though this book is filled with debatable opinion and redundant information, it's an important read. Read it if only to keep software engineering topics fresh in your head. Otherwise, if you are already experienced, it's kind of elementary.

Invaluable, Well Presented Information

Customer Rating:

There is probably not a whole lot to say about this book that has not been said already, but it certainly deserves another positive review nonetheless. I bought this book thinking that I did not have a whole lot to learn from it. I was certain I had read enough 'better coding' material in the past to know what good code was and how to produce it. I am sure you will not be surprised when I say that I ended up having a great deal to learn from this book. Almost all of the coding advice, design strategies, and debugging techniques are backed up with real research data. At the very least, this means that even if you know the advice is sound already, you can more easily introduce the topic to other programmers, or even to management, and it has a greater chance of being taken in to consideration. After reading this book, my code quality has definitely increased. I discovered that even the good practices I knew of before were not being put to effective use. The book is very specific. It does not typically give you vague advice that sounds good if you don't think too hard about it. It gives you very specific, concrete advice, with examples and data to back it up. The author seems to have put a great deal of effort into writing this book for every type of programmer (and even for people in software management positions). Every chapter introduction describes who should definitely read the chapter and who might benefit from simply skimming it over. He will also direct the reader to other chapters or specific sections of the current chapter based on the reader's knowledge and experience levels. Finally, as others have said, I consider this a must read book for any programmer.