On crap

Yesterday in studio around 5pm, Silvino drops by our desk. "Hey guys, what are we going to talk to Paul [our architecture systems professor] about in tomorrows meeting?"

Me: "What?" Followed by a pause where my brain catches up with reality and a series of expletives.
Silvino: "So when do you guys want to meet before?"

We decide to meet up after the architecture lecture that night, around 8.

I end up getting sidetracked talking to some AIA Young Architects members after the lecture. I'm a little concerned about the time so I excuse myself and begin to run upstairs. One my teammates, Kenny, waves at me from where he is standing in the food line. "I'll be up in maybe ten minutes," he says. Pappy's BBQ.  Upstairs I find a wiped out Dew and tired but cheerfully enduring Chuck. Trying to hold my panic, I print off the schedule for the rest of the semester and clutch it without reading it as a way to try to figure out what we're doing through osmosis. Tomorrows meeting is around 3, its not 9 pm, and I have to make a book for another class that happens at 11:30 tomorrow morning. I'm seriously freaking out. Kenny finally wanders back up with a plate of BBQ and I throw out some plans for how to proceed.

What I suggest: that each of us in a very loose way, sketch structural sections over the sections cut from the volumetric massing model, with perhaps the reference projects we were given in the last meeting as a basis of the structural system. Everyone agrees to take a shot at it.

What we actually end up doing: I make a clay model showing the domes and valleys in a wildly inaccurate way on a flat plane (the actual project is nestled into a hilly landscape). Kenny looks up some different case studies and collaborates with me to watch a youtube video of architect Peter Eisenman being a dick in a review of a student's work. (see below) Dew works on other classes, Silvino recovers from an all nighter, and Chuck comes up with a 3D model of a potential structural system that looks great. Yay teamwork.

My clay model is a mildly interesting and short lived distraction. Chuck's 3D model and structural idea becomes developed into what will be the core of the architecture. He definitely saved us this time. I've assumed a sort of leadership role in the group, but for this phase I feel like I'm really slacking. It's not like I'm the only one with outside classes, but my unfamiliarity with Rhino really makes it diffiucult to dive in and work directly with the crazy model.