Wednesday, 21 July 2010

Some scholastics

Today in class we spent hours discussing the following:
What is a concept?
Can a concept be compeltely fantastical or must it be grounded in reality from the earliest stage?
Is a concept temporal and dictated by time or does it have qualities?
Is set design architecture?
What is architecture?
What does an architect do? (*looks into reflection in fountain..."who am I??")
Is the design of a chair architecture?
Is a car architecture (being a space for inhabitation)
Is placing said chair in a room architecture?
Ditto a pot plant?
Ditto a horse
.... Believe it.

Anywho the upshot is an architect is faced with a cultural need and defines that need in order to provide a technical solution. ie we bridge the gap between client and builder/engineer (the boring dudes... sorry). I like this as it kindof implies we are jacks of all trades... and masters of none. We need to have just enough knowledge/skills to run round coordinating the specialist aspects of buidings. Which sounds bad but basicly it means I need to know about the existence of gravity loads and shit but won't be sued for them as I will never actually be working out the finicky requirements. 





See, the above image means crap all, except to fool the client (/tutor) into thinking we're masters of our discipline. Funnily enough, I will be getting my masters in architecture. Gosh I sound so cranky today. It was actually a really good class.

No comments: