Design Patterns: Elements of Reusable Object-Oriented Software

Design Patterns: Elements of Reusable Object-Oriented Software (also known colloquially as “Gang of Four”).

https://drewverlee.github.io/ i cover some (most) of the Design Patterns from the GOF book though the lens of Clojure. I stopped largely because i concluded the same thing Peter Norvig did many years ago, most DP in that book are work arounds for language limitations.

> build large systems DP are oft misused, but I think the main idea is a pattern language - a way to communicate to other developers what the architecture is. This is especially important on larger, more complex projects with more developers and developer turnover. Understanding the architecture of a project is crucial for grokking it, but usually not well documented. Even just "DPs are naming conventions" is helpful in this regard. I really disagree with the idea that most DPs are particularly clever or helpful - they are just the way you'd end up solving those kinds of problems yourself. If you look at your own pre-DP code, you'll see design patterns. What they give is a standardized terminology ("pattern language"). Sometimes an architecture seems more complex than necessary, but makes sense as you better understand the whole problem. e.g. how curl handles http. e.g. youtube-dl. (for me, when I reverse-engineered mini-versions of them, then studied their source) tl;dr "DPs are docs"

Agree on both those fronts, if you're not careful. Still dp influenced my coding more than any other book to date, which was the original question.

A remarkable classic http://www.amazon.com/Design-Patterns-Elements-Reusable-Obje... (http://www.amazon.com/Design-Patterns-Elements-Reusable-Object-Oriented/dp/0201633612) And Kent Beck's http://www.amazon.com/Smalltalk-Best-Practice-Patterns-Kent/... (http://www.amazon.com/Smalltalk-Best-Practice-Patterns-Kent/dp/013476904X)