Rating: 
Summary: Increases understanding exponentially
Review: A newbie to the world of professional C++ programming I had a strong academic knowledgebase, but no real world training. After a co-worker referenced this text, I decided to pick it up, and am I glad I did. Not only did my understanding of C++'s topics go through the roof, but I noticed myself writing more efficient, watertight code.The best plug I can give for this book is the following. Up to this point I've read 4 C++ texts in my young career, I can assure you it will be one that I reference the most in the future out of those 4.
Rating:
Summary: Invaluable tips for writting good C++ code
Review: Reading this book is about the best favor that you could do for yourself. Every page of this book is filled with sound advise on how to improve everything from your style of programming to the methods in which you use to get the job done effectively. This book is worth every cent I paid and has changed the way I code in C++. I highly recommend this book to anyone who is serious about writting efficient and effective C++.
Rating:
Summary: Great
Review: There seems to be a whole slew of books out titled "<adjective> C++" and I suspect this was the first. If not, it should at least be the model. The book is set up as 50 small chapters describing particular principles. Each is useful and clearly-presented in a manner that is not daunting. I've read many C++ books, including many of the <adjective> books and I have no problem proclaiming this as simply the best. Other books may cover more ground (Stroustrup's books, for example), others may be more current and others may be more advanced (I've recently been humbled by "Exceptional C++") but I think "Effective C++" is the most useful. If you're looking for a book to teach you the language, or if you're just learning the language, I'd say wait a little while before reading this book. If you've been writing code and haven't read this book, go for it. Although it's dated (pre-standard library) the concepts it covers are important ones that have not disappeared after standardization. I hope that when I write my book, "Extraterrestrial C++," I can do half as good a job.
Rating:
Summary: Essential reading for the intermediate programmer
Review: This book contains 50 pieces of good advice for improving your C++ programs. Each of the 50 items contains a concise discussion (usually about 5 pages) including examples. The 50 items serve as guidelines (as opposed to hard rules) for writing quality code, and the explanations give you an idea as to why the guidelines are important, and why they should usually be followed. I'd recommend this book to the programmer who's reasonably familiar with C++, but is not yet a "guru". (The gurus already have this on their bookshelf!). I'd also recommend it to the C/Java programmer who's learning C++, as it discusses a lot of potential traps that await the unwary C++ programmer.
Rating:
Summary: Excellent. A Must Read for any C++ Programmer
Review: The wealth of information in this book is absolutely invaluable. If you are already a C++ programmer, then this book will introduce you to new concepts and new ways of thinking when programming. A must-have for any professional programmer!!!
Rating:
Summary: Simply the best book on advanced C++
Review: This book is a must for C++ developers. It gives you a lot of insight as to why you should and should not do various things in C++. A lot of neat little tricks too.
Rating:
Summary: A Jewel
Review: First of all, let me explain to you why I consider Effective C++ as one of the best book I have ever red ! This book is technical, for sure. But scott meyer's way of "walking" through the explanation makes it nearly simple. Moreover, the style, with lot of jokes, makes it a pleasure. At the end, we've lost the feeling to have read a technical book. Incredible! As far as I remeber, I red the first edition several years ago, just after learning basic C++ feature: This book helps me to understand that we must know more than the syntax. That's why I recomand the book as a second level book, once you have learn C++ basis and even after few month of practice. ... Then Get it and enjoy !
Rating:
Summary: A very good book, although need to be updated.
Review: I think this is the first book a C++ programmer should read after reading a C++ syntax book. Every item is useful. This book is not as complete as <<C++ faq>>, but more concise.
Some items need to be updated, however. For example, Item 28, "Use structs to partition the global namespace", you can use namespace now (it is also mentioned at the bottom of the page). I think the items can be better organized, for example Item 23 "Don't try to return a reference when you must return an object" and item 31 "Never return a reference to a local object or a dereferenced pointer initialized by new within the function" can be combined to one, in item 23, "object" means a local object, it is better to say it explicitely. Also similar items are better to put closer, maybe it is difficult, since many items relate to each other. This is a book for intermediary level, it lacks some more advanced issues as exception, namespace, etc. Exceptions are discussed in its following book <<More effective C++>>, however, I would like to mention the discussion in <<more effective C++>> is not complete neither, up to now, I can find the most advanced discussions about exception in <<Exceptional C++>> by Herb Sutter, which is the book a advanced programmer should read. Discussion about namespace can also be found in this book. Overall, I think <<Effective C++>> is a good book for a serious programmer to start his/her c++ career, he/she can read <<More effective C++>> and <<Exceptional C++>> (maybe also <<Advanced C++ styles and idioms>> and <<C++ for real programmers>>) for more advanced topics/discussions, and <<C++ faq>> for a complete review of C++. I regret not being able to find a book for comparison of C++ and java, two most used programming languages. These two languages are similar in syntax, but have different features. For example, auto_ptr exists only for C++ and delegation exists only for java, The differences of languages affect the design and implementation, <<Design patterns>> discussed the design patterns with C++ and Smalltalk, however, Java is more popular than Smalltalk now and I hope to find a book which discusses the C++ and Java together. A more complete discussion of C++ advanced features is also needed, Herb Sutter is working on this.
Rating:
Summary: Absolutely required reading for every C++ developer
Review: I consider this to be *the* most important C++ book for the practicing developer. It's not a tutorial, but once you have learned the basic C++ syntax, this book should be on the top of your list. If you are a beginning or intermediate C++ programmer, you need this book. If you are already an advanced C++ programmer then many or most of these techniques may already be familiar to you, but you owe it to yourself (and whomever cuts your paycheck) to be sure. I also find myself consulting this book frequently as a reference. After you've read this one, get the sequel, "More Effective C++" for some more advanced techniques. These two books belong on every C++ developer's bookshelf. Period.
Rating:
Summary: Don't write C++ code without it...
Review: From beginning to end this book is packed with information that is IMMEDIATELY applicable. For example "Always declare destructors to be virtual" otherwise you may end leaking memory when subclasses are deleted. Or hiding the implementation of a class in an "Impl" that your class just passes through to. That way, if the implementation changes, the clients of the class are protected from recompilation. Beyond the wealth of just downright practical information the oragization is fabulous. The only other technical book that has organization as good as this one is "Design Patterns" There are several chapters such as "Memory Management" that have "Items" and each item has a few paragraphs describing the motivation for why you should believe Meyers with examples to prove it. Then there are solid examples that show the implemantation of an example usage. My company gave this book out with "Design Patterns" to EVERY developer in the company, and it was probably the smartest thing I've ever seen a company do. Read it and learn a TON.
| 
