First, I'll second brudger's point about scope. You say this is targeted at professional C++ developers, so you can assume a basic understanding of how C++ fea

First, I'll second brudger's point about scope. You say this is targeted at professional C++ developers, so you can assume a basic understanding of how C++ features work and restrict yourself to explaining how to choose and use those features to write reliable programs, don't feel any need for "completeness". You've got two sections, guidelines and design ideas. I would probably get the most value out of the design ideas section, as learning new patterns to do things well is always handy. But the guidelines section you're going to have to be a lot more careful. Most C++ advice books are targeted at beginners for a good reason, everyone has an opinion about how to write C++ best and they are rarely well supported. I would expect advice intended to be taken seriously by professionals to come with specific real world examples of how it addressed a reliability problem in a largish project, not just an expert author's say-so. If you could actually collect that, it would be incredibly useful. You could even give it a nice inflammatory title like "n C++ mistakes that have wrecked projects"