If you say the book “covers correctness and understandability in nearly every paragraph” then I’m convinced we must be talking about different books.

For example, the book presents a rule for class names:

> Classes and objects should have noun or noun phrase names like Customer, WikiPage, Account, and AddressParser. Avoid words like Manager, Processor, Data, or Info in the name of a class. A class name should not be a verb.

What a proclamation! We could connect this to correctness and understandability. But the book does not. You could say that it is harder to understand a class named “SomethingManager” because “manager” is vague, and more specific words are usually preferred. Instead, the book presents a rule, without explanation or example. Kind of like the Strunk & White book on style, and if you like Strunk & White, then we disagree on at least two books.

That’s my general complaint about the book. Too many proclamations, too much doctrine, not enough explanation or foundation.