Last night, I joined J and another computational designer for dinner with some heads of the architectural software firm Rhino. (Yes, I was there just for the free food) J and his friend have been showing some Oregonian architects what's up with scripting in 3d and this was a dinner to celebrate their success. Now, personally I'm fascinated with how designers "think" in the digital design atmosphere. (I've written a little about it in an article that will be out next year) CAD is so Cartesian: the circuit of hand and eye is disrupted not just by a pencil but a bunch of algorithms, a pregiven geometry and a certain order in which designers can create form, volume, lighting and texture. (an order quite backwards to which they might work in the 'real' world: volume and texture come at the end for example)
So I've been mulling all this over and thinking that Rhino which uses a different geometry and nerbs modelling system is a good alternative to allow a little variety in the methods for making the built world. ... lest everything look like a textureless CAD fly-through. The CEO s of Rhino are pretty proud of their product... but surprisingly to me, they didn't seem to think much about the long-term implications for (and restrictions on!) design and the built world. They felt they were creating a neutral tool that just let architects do better what they'd always wanted to do. In no sense did they feel the tools prescribed design ... even when J pointed out that it was a little bit odd and awkward to think about volume after form.
I imagine art historians of the future looking back at the last 10 years of architectural design and excavating not tools, but scripts and codes. They'll be trying to figure out which version of Rhino or Grasshopper a designer might have access to in 2007 or 2013 in order to invent as they did. They'll be thinking about how space became something we understood in relation to the fly-through tool.
But it was a great lesson to me that Rhino developers didn't need to think about any of that to make the built-world altering tool they've created. Nor do they want to think about it in order to sell more or refine it. And they certainly aren't reading anything coming out of architectural theory ... yet again (pace my post yesterday), there seems to be a one-way sort of conversation between theory and practice, humanities and technology.
2 comments:
I'm in complete agreement, of course. (You can tell when a building is made in Rhino.)
But to play devil's advocate, there's the architect who thinks *too much* about theory and not enough about making beautiful things.
for sures. but these guys weren't architects: they were software designers with -- in my humble opinion -- plenty of time to reflect on what they were helping/preventing others from doing.
Post a Comment