Rating: 
Summary: Excellent purchase for any C++ programmer
Review: I'd recommend this book (and the subsequent "More Effective C++) to any serious C++ developer. It gives sage guidence in the most common areas in which novice C++ programmers make mistakes. If I were a C++ project manager, I would ensure all of my developers read this book at least once. Meyer's style isn't everyone's cup of tea - sometimes amusing, sometimes tedious; but you simply cannot fault the man on his mastery of C++ Whilst this book would almost certainly propel a C++ novice's code up to the next level of quality, experienced developers should know this stuff. However, I've personally worked with several 'experienced' (> 2 years) C++ developers who admitted that they had more than one 'light-bulb moment' after reading Meyer's books. This is a testament to Meyer's readable style and ability to explain C++'s more esoteric elements (time for a coffee break, perhaps?). The book works well as a reference guide when developers have that "I know there's a better way to do this..." feeling. Overall, an excellent buy - well worth the money.
Rating:
Summary: Packed full of useful insights and explanations
Review: The first edition was incredibly helpful in grasping key concepts. The second edition is even better. Rarely have I ever come across a book that so effectively communicated a technical subject. Not only is it informative and educational but enjoyable. The reader needs to understand C++ syntax and basics, but this book will then help you take your understanding and your programming to the next level.
Rating:
Summary: A MUST-READ for all C++ Developers
Review: As a C++ instructor, I spend a lot of effort searching for good books to recommend to my students. *Effective C++* and *More Effective C++* are two books that I think every C++ developer should own. The writing style is fantastic and the presentation of the material is very approachable. The topics are arranged as "Items" that are organized around particular programming ideas instead of language features. The material is suitable for many experience levels: beginners to experts. Easy Decision for Today: Just Buy It
Rating:
Summary: A must-read for serious C++ programmers/managers
Review: If you are serious to use C++ in any OOP projects, this book is a must-read. It gives you insightful information on various aspects of C++ programming and is both easy to follow and practical. I have applied the techniques presented in this book both at work and in class (for my students) and have found it indispensible
Rating:
Summary: Title could be "50 Ways to be Nice to Co-Developers"
Review: Well written C++ books are rare to start with, this is an example of a more rare and more precious thing, a well written practical C++ book for software engineers.
I strongly recommend this book to any developer I work with as basic self-defence. Not only does it give marvelous design and coding advice, but it explains the basis of each guideline and how and when to apply them
Rating:
Summary: An excellent book on the proper way to write C++ programs
Review: I highly recommend Scott Meyer's book to anyone who is serious
about programming in C++. It is well-written and easy to read. Most
points are demonstrated with clear examples. Many of the points
are relavent to object-oriented programming in general
Rating:
Summary: A great book, esp. if you have used C++ for several months
Review: I've looked at lots of C++ books, both beginning and
advanced. This one was perfect for me to improve my C++
programming style, effectiveness, understanding, and power after I had been working in C++ for awhile. Yet it is
very readable and interesting. This is in sharp contrast
with most C++ books that are either too simple for a good
programmer, or go into amazingly complex examples and programming techniques, thinking that THAT means they're
advanced. I highly recommend this book.
Rating:
Summary: 50 Specific Ways
Review: A must have for anyone serious about C++.
Rating:
Summary: Great
Review: There seems to be a whole slew of books out titled " 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 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: If you're developing in C++, you need to read this book
Review: C++ can be a language fraught with peril. Leave off a "virtual" in the wrong place and you've created a memory leak. Forget to implement a copy constructor in a particular class and you've created a corrupt heap waiting to happen. In this book, Scott presents guidelines on 50 C++ topics covering a broad range of subjects: how to avoid the C++ pitfalls mentioned above, how to write better code, how to effectively use C++ constructs in your OO designs, and more. Whether you're a newbie or an expert, there's substantial meat in this book for you. Scott's easy-going writing style makes the explanations easy to read and digest. Unlike other books I've read, Scott provides detailed explanations allowing you to really understand the topic at hand. The 50 items are self-contained chunks of information, each thoroughly covering a specific topic. C++ developers working for me are required to read this book (and Scott's companion, "More Effective C++") before I let them write a line of production code.
| 
