- - The original note follows - -
From: randolph@xxxxxxxxxx (Randolph Fritz)
Subject: Re: Architecture School of the Future
Date: Wed, 20 Apr 1994 16:46:08 GMT
In article <2p1s67$8s@xxxxxxxxxxxxxxxxxxxxx>, HughJC <hughjc@xxxxxxx> wrote:
>
>This sounds interesting as long as you don't forget about the low tech part of
>architecture. 75% of my time (as an architect for 15 years) is spent LISTENING
>to people (clients, regulators, bosses, etc) and WRITING (reports, letters,
>proposals, apologies, etc). These were two skills which were inadequately
>stressed during my college experience. Don't make the same mistake that they
>made in Medical Schools years ago, concentrating so much on the technology and
>forgetting about the people skills.
I think that's an excellent point; in my research on the profession,
before I decided to start working towards a career change, I found
that interpersonal skills were at least as important as design
skills--a good chunk of the job is client relations & project
management. One of our teachers, Hugh Lorimer of (I think) K+CZL,
talked some about his work with computer design tools & one of the
things that came through most clearly in the discussion was how much
impact they had on communications--how being able to do even sloppy 3d
drawings in real-time made it possible for the client to participate
in design, how they affected to way designers worked with each
other, and how what was handed to the contractors was now a 3d
computer model which the contractors, in turn, marked up.
On other aspects of this: I think it's likely that in the future that
model will go from design to construction to a facilities computer
right in the building; in essence that buildings will have "minds" of
a sort. This promises to present interesting new design problems.
Randolph
From: randolph@xxxxxxxxxx (Randolph Fritz)
Subject: Re: Architecture School of the Future
Date: Wed, 20 Apr 1994 16:46:08 GMT
In article <2p1s67$8s@xxxxxxxxxxxxxxxxxxxxx>, HughJC <hughjc@xxxxxxx> wrote:
>
>This sounds interesting as long as you don't forget about the low tech part of
>architecture. 75% of my time (as an architect for 15 years) is spent LISTENING
>to people (clients, regulators, bosses, etc) and WRITING (reports, letters,
>proposals, apologies, etc). These were two skills which were inadequately
>stressed during my college experience. Don't make the same mistake that they
>made in Medical Schools years ago, concentrating so much on the technology and
>forgetting about the people skills.
I think that's an excellent point; in my research on the profession,
before I decided to start working towards a career change, I found
that interpersonal skills were at least as important as design
skills--a good chunk of the job is client relations & project
management. One of our teachers, Hugh Lorimer of (I think) K+CZL,
talked some about his work with computer design tools & one of the
things that came through most clearly in the discussion was how much
impact they had on communications--how being able to do even sloppy 3d
drawings in real-time made it possible for the client to participate
in design, how they affected to way designers worked with each
other, and how what was handed to the contractors was now a 3d
computer model which the contractors, in turn, marked up.
On other aspects of this: I think it's likely that in the future that
model will go from design to construction to a facilities computer
right in the building; in essence that buildings will have "minds" of
a sort. This promises to present interesting new design problems.
Randolph