A useful and interesting collection of guidelines for writing C++. Some of the guidelines are "obvious," but his other reviews have noted, worth repeating. Others are not so obvious and demonstrate subtle traps. One big flaw is that, particularly for the subtle cases, they don't go into enough detail -- they explain that something is bad, maybe even give an example, but not enough to really understand The intricacies of why.
I felt that Scott Meyers' books did a much better job of explaining the why, and where they overlap, you should read his first. Unfortunately, Meyers doesn't cover everything.