Pretty much everything in the series Fowler edits on design patterns is essential IF you are working with frameworks/projects that use those patterns. E.g. PoEAA makes Rails make sense because Rails is literally selections from PoEAA verbatim.
Sometimes I wish folks would recommend reading some of the other patterns books before Design Patterns. Like Pattern Hatching, about what patterns are how to document them when you find them.
Or Smalltalk Best Practice patterns which is the best patterns book ever, even if it's a bit niche😂
One of my perennial aims when composing educational resources is to point younger devs back to classics. The amount of time I see wasted on game-of-telephone interpretations of concepts that were actually explained *really well* in their source material is substantial.
Comments
* POODR
* XP Explained
* Refactoring
* Design Patterns
* Pragmatic Programmer
And, no, I didn't get Design Patterns until I read other books on the subject. Back to that thing about some authors speaking to you and others not.
* Domain Driven Design
* Working Effectively with Legacy Code
* Growing OO Software
Pretty much everything in the series Fowler edits on design patterns is essential IF you are working with frameworks/projects that use those patterns. E.g. PoEAA makes Rails make sense because Rails is literally selections from PoEAA verbatim.
Or Smalltalk Best Practice patterns which is the best patterns book ever, even if it's a bit niche😂