architecture

You are currently browsing articles tagged architecture.

I just saw that the BBC tv documentary series based on Stuart Brand’s “How Buildings Learn” has been posted on Google Video. Huzzah!

It’s been a while since I read the book, so I watched a bit of the first episode, and it kicked up a thought or two about the language we use for design. Brand makes a sharp distinction between architecture that’s all about making a “statement” — a stylistic gesture — and architecture that serves the needs of a building’s inhabitants. (Arguably a somewhat artificial distinction, but a useful one nonetheless. For the record, Joshua Prince Ramus made a similar distinction at IASummit07.)

The modernist “statements” Brand shows us are certainly experiences — and were designed to be ‘experienced’ in the sense of any hermetic work of ‘difficult’ art. But it’s harder to say they were designed to be inhabited. On the other hand, he’s talking about something more than mere “use” as well. Maybe, for me at least, the word “use” has a temporary or disposable shade of meaning?

It struck me that saying a design is to be “inhabited” makes me think about different values & priorities than if I a design is to be “used” or “experienced.”

I’m not arguing for or against any of these words in general. I just found the thought intriguing… and I wonder just how much difference it makes how we talk about what we’re making, not only to our clients but to one another and ourselves.

Has anyone else found that how you talk about your work affects the work? The way you see it? The way others respond to it?