Rating: 
Summary: I'm torn.
Review: Well, first, just because Microsoft has lots of buggy code doesn't mean that someone there doesn't know what he's doing and can't write a book that's really good. This book is worthwhile, though not perfect.I'm sorry it took me so long to get around to reading this book. There were several things in it such as its tips for memory management that I could have been doing all along that I've never really done. Now I'm going to try to adopt a lot of the tips. I liked the material the book covered, even if some of it felt outdated. I think my biggest problem was that it seemed like the book should have covered a lot more material. For example, I wanted to have heard an opinion on things like UML, even if the author didn't end up liking it and teaching it. I've never done that kind of stuff, but there are a ton of books I've thumbed through that seem to think it's the way for more reliable code, so I think it merited some discussion. I think everyone has a lot to learn from this book, but I hope something better shows up (maybe a second edition?)
Rating: 
Summary: Just look at the publishing date.
Review: You are looking at a 10-year-old book with a bunch of green screens on the cover. What more can I say. I bought it in preparation for an interview with Microsoft. I did not find it helpful, except for a few pages that do help understand Microsoft culture (but you can learn much more about that on the net). So many new things have appeared (and/or became popular) since the book has been published. OOAD, C++, Java, RUP, XP, design patterns, to name a few. It puzzles me that Microsoft still recommends this book.
| 
