Rating: 
Summary: Kewl best practices, not just punctuation rules
Review: In addition to all the usual rules about proper capitalization, indentation, comment styles and such, there are actually 42 pages on good Java design and coding practices (defining subclasses that can be used wherever their superclass can be used, always constructing objects in a valid state, exceptions, assertions, really good rules for synchronization, lazy instantiation, etc.) There is also a very short chapter on packaging. There's a lot of forehead-slappers in this very portable book.
Rating:
Summary: Ideal for coders from students to experts
Review: In the Spring semester of 2003, I am teaching a class in software engineering and the students are creating a large program that is to be written in Java. Not all of the students are experienced in Java, so they are required to learn the language as they follow the rules of software development. At the time when the textbooks were selected, I was not aware of this book and that is unfortunate. It is an excellent quick reference to a set of rules that will point you in the direction of much cleaner and efficient Java code.
In all future classes where I am either teaching Java or having the students use Java to write large programs, this book will be a required acquisition. I have already placed it on my textbook list for software engineering in the Spring of 2004.
Rating:
Summary: How often does $10 get you a usefull programming book?
Review: It is rare that you can spend about $10 on a computer book and have it be a valuable addition to my library. This book is small (I was kind of shocked when it first arrived) but it has a lot of usefull information in it. Valuable tips provided in a very concise presentation. If every Java developer followed the rules in this book, code would be easier to read, understand, and maintain. A must for those who develope Java in teams.
Rating: 
Summary: bad, very bad
Review: it's only recommended for the most begginer of the begginers, in general programing not only in java.
Very bad for me and, i think, everybody that has already written and seen any code in any language.
Wasted money. example:
this is not right if (something) {
do one thing
do another thing
} this is right if (something) {
....do one thing
....do another thing
....} i guess, everybody knows this.
Rating: 
Summary: Good Resource
Review: Provides a good resource for the intermediate to experienced JAVA programmer. Gives area of concentration to make a professional product. A copy should be available to any group of professional developers working in JAVA.
Rating:
Summary: Deserves 0 Stars
Review: Read Code Complete by Steve McConnell. You don't need this book. It contradicts itself on several occasions and is totally wrong on others. It's unfortunate and sad how many organizations want to adopt texts like this as their "coding standard". A pamplet-sized book of bullet-points can't make developers competent, but a comprehensive manual of the best in software engineering practices like Code Complete can.
Rating:
Summary: All the right elements
Review: This book came along at the right time for me. It has all the right ingedients for standardising team coding styles and developemnt methods, including simple descriptions for their use. I recommend it to those in a similar situation or those who are looking to standardise their coding approach and create best practice standards. The real plus factor is that the book is small enough to read in a day, yet useful for a life time!
Rating:
Summary: Exactly the book I was looking for
Review: This book contains all the right comments for adopting good programming practices. I needed the book for deriving a common coding style in our company. After reading the book I immediatly ordered a copy for each one of our developers. I wish there was an electronic version of this book which I could put in our intranet.
Rating:
Summary: It does what it says it does.
Review: This book does exactly what it says it will - it gives you a series of coding standards to rely upon for team coding. The book is not, however, very heavy on theory. There's is only brief discussion about why each standard was chosen, and in my opinion, several of the standards are not optimal (particularly those relating to the indentation of code). This brings up the further problem that to be useful as a reference manual, your team must adopt the standards. But this book will give you a quick and easy starting point for coming up with your own coding standards.
Rating:
Summary: Great little book.
Review: This book is a great compilation of many many little "secrets" and techniques from real Java projects. Chapters about documetation and packaging are really really good (the later is just 6-7 pages long but those are probably the most concise 6 pages I've ever read about package designing). If you read Sun's coding style recommendations for Java (available on Sun's site) and liked it, this is the book for you. It covers all other aspects of java programming using the same style.
| 
