Wednesday 1 February 2017

Precedents and references

Precedents and references

Design precedents are something that has been on my mind for a long time - not that I've done much work about them. The main reason is that precedents require quite a lot of work: collecting information in some detail; organising collected information in a way that makes factors, features and internal relations explicit; building on this organisation to make some of the reasoning behind the design; connecting the precedent to its own precedents as well as antecedents (including new designs). These tasks are quite demanding.

However, probably the biggest problem is the loose manner in which even design theorists treat precedents: they might call any reference a precedent, ignoring the need for structural similarities that reveal rather than mythologise. This is probably indicative of the weaknesses of architectural and design theory: theorising comes easy in creative areas. Any successful designer or teacher can find an audience and present some view that immediately becomes gospel. Forget validation and verification, the view doesn't even have to have internal consistency. In such as mess, the really worthwhile ideas (and there are enough of these to develop a real domain theory) simply disappear in a sea of vogue and nonsense. What's the use of trying to have a proper definition of precedents and references in this framework?

No comments:

Post a Comment