An opinionated thorough demonstration on how to write C++ at scale. I didn’t agree one all aspects, though I have to admit it was the first book on C++ that clearly stated _how_ to actually design stuff both on a physical as well as on a logical level. Something which most other books on C++ won’t get into. All that being said I think it was pretty relevant for medium to large codebases

Not at all.

It has exactly one obviously useful piece of advice: don't make circular dependencies between libraries. In practice, that means organizing in layers.

Most of us don't depend on many libraries where the authors of the libraries know one another, so it is easy to follow, even by accident.

It has lots and lots of obsolete advice, though.