Campbell Ritchie wrote:Why do you think there is a gap between beginners' OO code and fancy design patterns?
In my humble opinion and experience (which is not big, I'm still a student, which I based upon reading HF Design Patterns and few implementations of patterns from the book), beginner's OO code is not so flexible and resilient on changes of functionalities, while (fancy) DP most certainly are. From that standpoint, and as someone who is at least trying not to write procedural code but an OO code, I was wondering in what degree are guidelines for good OO code in Matthias's book, (resilient to changes), are close to designing classes and interfaces, putting them together if you will, like in some (fancy) DP.
Campbell Ritchie wrote: Good OO code will always use patterns, even if the patterns are too simple to have a name, even in a one‑class app. The common or garden OO class is a pattern in its own right, even if nobody calls it a pattern.
Learn something new. Completely makes sense.
Campbell Ritchie wrote: Maybe you meant to ask how far the book goes taking people from the basics of OO to design patterns.
We could phrase it that way, yes.