Most of the author's views (like, for example, on writing comments) are non-controversial. He does however, coin the terms "deep" and "shallow" to talk about the way modules are structured. I think these are very useful, and should be commonly known!

Other than that, the author sticks to the semantics of the vaguely object-oriented curly brace languages. Java, C#, Go, etc. I think this book could be richer if the examples were drawn from a greater variety of programming languages.