Not quite. I mean, it is an interesting book - functional programming idioms applied to C++ templates which gives you an interesting [generative] techniques applied to several GoF design patterns, but it is not an everyday C++ code you write. I'd say, for general C++ good style, Bjarne's works are more useful. At least, to start with.
Need a "C++: The Good Parts" compiler (or static analysis front end) that enforces the good parts but your code is a compilable by a C++11 compiler. I've heard some Rosy developers joke that Rust is C++ The Good Parts. :)
The problem is that "The Good Parts" vary from team to team and from domain to domain. One of the strengths of C++ is that it can fill all those needs. This is important because often the problem you start out solving is different than the one you need to solve.
