Tag: Clayton Muhleman

A new exhibition opens next week at the Hubbell Street Galleries in San Francisco, part of the California College of the Arts, called Drawing Codes: Experimental Protocols of Architectural Representation. The idea behind the group show is to look at “the relationship between code and drawing” (emphases theirs), or “how rules and constraints inform the ways we document, analyze, represent, and design the built environment.”

Drawing Codes is curated by Andrew Kudless and Adam Marcus, with Clayton Muhleman, and it features work by Erin Besler, Elena Manferdini, Jimenez Lai, the Oyler Wu Collaborative, Rael San Fratello, and many more.

As Kudless—of Matsys fame—pointed out to me over email, the curators “gave all of the participants a set of codes that they had to follow (e.g. all black and white, orthographic projection, 25″ x 25″, etc.),” using this set of constraints to, among other things, foreground differences in approach between each participating architect.

If everyone’s doing the same thing, then how each person does it becomes more revealing.

Perhaps ironically, it was actually the drawing by Kudless himself—which I first saw on Instagram—that caught my interest.

Called “The Walled City (10-Mile Version),” that project imagines an entire metropolis that is nothing but one, continuous wall.

Kudless explained that it came about by posing himself a rhetorical question: “What would a city look like if it was a wall and nothing else? I’ve been fascinated with walls that have grown thick enough to be buildings in themselves. From medieval European city walls to the Great Wall in China, there is something really interesting about taking something that is ostensively about separating two territories and turning into an inhabitable space in its own right.”

The results: a rule-constrained exploration of how a wall could become a city.

I started to play around with slowly increasing a wall’s length while preventing it from moving outside a site or intersecting itself. At a certain point in the growth process, the wall takes over the entire site. There is still an inside and outside to the wall, but sometimes the outside is deep inside the site boundary or vice versa. At that point, I was left with a big squiggly wall, but realized that I needed some sort of roofscape to make it read as a city and not just a thick wall. That’s when I turned to Google’s autocomplete feature to give me suggestions on what programs [spatial functions] a rooftop might support. I worked my way from A to Z pretty much accepting whatever suggestion Google’s autocomplete gave me and started designing parametric definitions that could implement that program on a number of different sites along the wall’s top.

Interestingly, Kudless also pointed out that, if he were to run the same generative script again, it would likely produce “a similar, but not identical city,” and it would almost certainly not result in a wall exactly ten miles in length (which, in this case, was purely a coincidence, he explained).