Customer Rating: 
Summary: A suitable choice for the commandments of software development
Comment: There is strong evidence to support the claim that software development is the most difficult endeavor humans have ever embarked on. Humans are hard or perhaps a better term is soft wired to make errors. It is this capacity for errors that allows us to develop new things and improve performance. Unfortunately, software development is extremely precise, which is in opposition to how humans generally function. Therefore, it is practically impossible to develop large-scale software projects that are error free.
The solution is to manage the errors so that the types of errors are skewed toward the less serious and the probability of serious errors is reduced to an achievable minimum. This requires the development of a process, which is constructed from a set of fundamental principles. 201 of the most effective principles are briefly described in this book. All are at most a couple of paragraphs in length, and are self-evident to the experienced coder. However, self-evident does not mean redundant as the pressure to relax a principle can become overwhelming under the rush to complete. Software designers and their managers need constant reminders that short cuts to code creation are misnamed. There is no such thing, yet it is easy to rationalize that your case is different and it will work this time.
This is a book that should become the commandments of software development. Each person in the team should have a copy and when it is suggested that a principle be violated, the appropriate red flag should be raised. By doing that, while the simple problems will still exist, the more complex ones will be avoided.
Customer Rating:
Summary: Who says life doesn't come with instructions?
Comment: It does, as far as your life as a software engineer or manager thereof goes. This book spells out everything, from getting started on a project to maintaining it after release.Each principle is given as a heading, each on a separate page, and every one of them is true. A short explanation follows each one. Other principles that relate are pointed out. But the true value is the footer on each page. It is a pointer to the literature where you can find the principle in question discussed definitively.
Ultimately, this book functions as a directory/index to every aspect of software engineering. If you need to know a phone number, you look it up in the phone book. If you need to know something about software engineering practices -- you can look it up here.
Customer Rating:
Summary: The One Minute Software Manager
Comment: This book summarizes 40 years of software's best practices into 240 pages. Short, sweet, to the point, and incredibly valuable. High recommended. I browse it about once a week and pull out a gem or two every time.
Customer Rating: 
Summary: Good book, excellent idea...
Comment: This is a very good book for revising, or better to keep you with everything fresh in memory. Most of the tips are those that when you read you say "I know that" or "That's obvious" but the point is exactly that, to remind you of the 201 obvious things that you should be doing on daily basis at work but your not.
Customer Rating:
Summary: Good, but unoriginal.
Comment: As someone else already mentioned, the book is mostly a bibliography to other books. Skip this book and head straight to the definitive source for software engineering, Steve McConnell's "Code Complete".
