It's easy to dismiss the GoF Design Patterns

When I first read the gang of four's Design Patterns I dismissed most of it as a coverup for the unfortunate parts of C++'s object design. That was definitely unfair, since the strongest benefits of Design Patterns come from managing huge code bases, a fact that I missed with all the small examples.

But even still, I would love a book on design patterns that is built for modern interpreted languages, with duck-typing and no type checking.


(Commenting is closed. Please tweet me at @landedstar instead.)