Return to index: [Subject] [Thread] [Date] [Author]

Re: Architect vs. Engineer

[Subject Prev][Subject Next][Thread Prev][Thread Next]
an oldie but goodie

Structural Engineering is the art of molding materials we don't wholly
understand, into shapes we can't fully analyze, so as to withstand forces we
can't really assess, in such a way that the community at large has no reason
to suspect the extent of our ignorance.

attributed to Jim Amrhein

----- Original Message -----
From: "Jamie Heupel" <jheu(--nospam--at)raaschassoc.com>
To: <seaint(--nospam--at)seaint.org>
Sent: Friday, March 02, 2001 6:25 AM
Subject: Architect vs. Engineer


> Fellow Engineers,
>
> What's the difference?  I just read the definitions of Architecture and
> Engineering from Funk & Wagnall's Standard Desk Dictionary and can see why
> laymen are confused or unaware with what WE do.  The definitions are as
> follows:
>
> Architecture:  The science, art, or profession of designing and
> constructing buildings or other structures.
>
> Engineering:  The art and science of designing, constructing, and
operating
> roads, bridges, buildings, etc.
>
> Ouch!, that must make me an Architect and an Engineer.  Since I am already
> a "Son of an Architect" by birth, does that make me half Architect and
half
> Engineer?
>
> I have used the same simplistic definition that Roger Turk used in
> yesterdays email:
>
> "An over simplified explanation of a Structural Engineer that I use, is,
> "The
> Architect draws the pretty picture, and the Structural Engineer figures
out
> how to hold it up."  (Sometimes I think even that is too complicated for
> some
> people.)"
>