> If code is broken due to it being bad abstractions, you will need to know how it is implemented regardless. Sure, but the type (and thus the guideline) is st

> If code is broken due to it being bad abstractions, you will need to know how it is implemented regardless. Sure, but the type (and thus the guideline) is still helping with that instead of hurting. I can much more easily find all usages of a broken `Month` type than I can an int representing a month which could be named anything. > That said, I still will never follow anything religiously, even if Bjarne Stroustrup wrote it because really no rules fit every situation Oh definitely, I don't agree/follow all of those guidelines either. The guidelines themselves don't pitch themselves as that, and many of the "rules" have whole sections listing reasonable exceptions and why those exceptions are OK.