New York Institute of Technology (Max)

  • anchor

    D6 – review (?) and visit

    By l8rpeace
    Feb 22, '07 2:02 PM EST

    So, probably the least anticipated entry I have made, commencing with the models from last time:

    model progression

    And, the notes I took during the review:


    There was a lot of mention thrown around of what a project is “about.” So I made note of all mention that day.

    For the next class, we had visits from different engineers. The current focus is on structure (of which, as you probably noticed above, I have little of in the model). We had representatives from Arup, Guy Nordenson, and Front, and here are the notes from their presentations, in order (they covered a multitude of buildings).


    So now the question remains: how does this change my approach? Some of the problems were very sustainable (Bed Zed) and some not sustainable at all (Toledo Glass Museum). But what struck me was the influence the engineers had on the design. It seems like architects create problems and engineers fix them. I suppose I could be wrong, but something about that rings particularly true with me: when I was a software and network engineer, I fixed problems that people couldn’t even necessarily articulate, and that, in their particular (and sometimes arcane) workflow, they had created for themselved. For instance, yes, Arup fixed the problem of thermal loss in Richard Meier's atrium for Phoenix, but why did the atrium need to be so grand and tall? Front and Nordenson accomodated the curvilinear forms of the glass walls in Toledo, but every time a piece of glass breaks, it needs to be bought in Germany, fabricated in China, and then shipped to Ohio. Also, while the presentations showed how form changes through structure, there seemed to be an overwhelming notion that the architects either approve or disapprove of how a structure is implemented (how something stands up), but they give little thought to actually designing said structure.

    More models for tomorrow.


    • a friend/collaborator from arup once told me that while he enjoyed dealing with the problems that architects create he would never be able to think of the designs that caused them in the first place, and didn't see us architects in the way you describe above.

      he was responding to my question as to why he didn't become an architect himself, cuz his work was so creative and interesting in its own right... i was surprised by his response.

      you might be surprised to find that engineers do not make good architects, and need us as much as we need my friends case, the partnership is very fruitful from a professional perspective. the partnering of ambitions and skills works very nice...which is i guess how it is supposed to be...

      Feb 22, 07 5:23 pm  · 

      nice sketches

      Feb 23, 07 12:24 am  · 

      ^^^I second that, makes me wish I would sketch more than I write when taking notes, so much clearer when you look at it a second time. By the way parametric modeler is Catia, its very powerful program if you have the patience to learn it.

      Feb 23, 07 10:34 pm  · 

      Block this user

      Are you sure you want to block this user and hide all related comments throughout the site?


      This is your first comment on Archinect. Your comment will be visible once approved.

    • Back to Entry List...
  • ×Search in:

Affiliated with:

Authored by:

  • l8rpeace

Other blogs affiliated with New York Institute of Technology (NYIT):

Recent Entries