4 ms·
I sympathize with the critique of GoF design patterns, but the author is seriously distorting Alexander in his eagerness to dissociate him from them. "How can y
by gruseom 18y ago
I sympathize with the critique of GoF design patterns, but the author is seriously distorting Alexander in his eagerness to dissociate him from them. "How can you distribute responsibility for design through all levels of a large hierarchy" is not the theme of A Pattern Language, which is easy to see when you consider that the book is largely about dwellings (which don't involve any large hierarchies).
I agree, though, that the most interesting aspects of Alexander never made it into GoF. His key insight is that buildings should be designed around what makes humans feel more alive in them. Applying that to software, you'd end up thinking more about projects and teams than about iterators or singletons.
Another aspect of Alexander that's relevant to programming is his exploratory approach to making buildings. As I understand it, he never designs anything up front. Rather, he studies the site, talks to the people, and builds a little at a time, allowing the thing to emerge in a way that is appropriate.
- michael_dorfman 18y agoI agree that "large hierarchies" may be an overstatement, but it is worth remembering that Alexander does not concentrate total responsibility for the design of a signle in the hands of a single architect, or even a firm of architects, but rather, involves a large number of "end-users"-- and then iterates this notion both upward (to city planning) and downward (to interior design of individual rooms), so while the "hierarchy" may be relatively flat, the problem of distributed responsiblity is a real one (and a relevant one for software).
- michaelneale 18y ago>His key insight is that buildings should be designed around what makes humans feel more alive in them. Applying that to software, you'd end up thinking more about projects and teams than about iterators or singletons. No - I think you would end up thinking more about the end users of your applications.
- gruseom 18y agoYeah, good point - that's a much better way to draw the analogy. (For some reason I missed this comment when the thread was current.)