Her book with Katrina Owen “99 Bottles of OOP” lays out an even better case for this I think. Particularly useful is the introduced language to help measure the state of a codebase (“shamelessly green” vs “incomprehensibly concise” etc).
Also quite like Fowler’s observation in Refactoring that (to paraphrase) abstractions are earned, not enforced.
Also quite like Fowler’s observation in Refactoring that (to paraphrase) abstractions are earned, not enforced.