Wednesday, September 23, 2009

031 The Problem with Lambda


We’re back making architecture this week. The project was introduced to the press, we went public ... Now it’s time to get going [Seriously]. The problem we are facing is that a portion of the design  was represented conceptually. There is a major component that is explicit and readable as architectural form. And then, there is another that is suggested rather than clearly stated [it's complicated].

Obviously, put the two together and you create a certain ambiguity. For people “in the know,” it’s completely fine and may even be playfully stated, but for the common “man” it is somewhat confusing. They default back to trying to connect the forms to something they know, something they are familiar with . And if our model and renderings mix explicit representation with implicit meaning things just get impossible to sort through. The goal was simple, the intent clear but the resolution was ambiguous.

No comments: