Hacker News new | past | comments | ask | show | jobs | submit login

I think a counter-example of that type of architectural criticism is the work of Christopher Alexander; he's extremely opinionated about what he likes and doesn't like, but in "A Pattern Language", he lays out a bunch of design principles and explains what problem they solve and why he thinks they're the optimal solution to that particular problem.

Any other architect can come along and say "I don't think that's a real problem" or "I think I have a better solution to that problem". There's no appeal to authority (e.g. "this is how architectural tradition says you're supposed to design things, and anything that breaks these rules is wrong"). Everyone is encouraged to work things out on their own from first principles and see if they come to the same conclusion. I think this is especially important in Architecture, where anything beyond basic utilitarian functionality is very tied to psychology and is therefore in a realm of conjecture where very little is definitively provable and yet many people seem to react very similarly to certain design elements.

In "A Timeless Way of Building", Alexander talks about cultivating the mental discipline of separating what you think ought to be a good design from analyzing your actual emotional response to that design. Learning to pay attention to the latter instead of the former can often lead in unexpected directions and result in better design.




A Timeless Way of Building is a fantastic read for architecture enthusiasts. Also, it's easy to see how that book influenced software since the GoF book is very much the same idea applied to software.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: