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

RE: Something That Bugs Me About The AISC Code

[Subject Prev][Subject Next][Thread Prev][Thread Next]
You're right, I was unclear. I guess what I'm complaining about is really
beyond anyone's ability to fix. That is, that although we as structural
engineers have a "right" as well as a "duty" to use our best judgement in
the solving of such "non-standard" problems, in the end it always comes down
to a clever lawyer (in the even something goes wrong).

I can say "I based my design procedures on this accepted code or standard"
and Mr. Shyster can say "ah, but doesn't that code say it's for BUILDINGS?"

I know why AISC put those disclaimers in there, but it makes for a dilemma.

William L. Polhemus, Jr., P.E.
Polhemus Engineering Company
Katy, Texas
Phone 281-492-2251
Fax 281-492-8203


-----Original Message-----
From: Christopher Wright [mailto:chrisw(--nospam--at)skypoint.com]
Sent: Tuesday, May 15, 2001 10:18 PM
To: SEAOC Newsletter
Subject: Re: Something That Bugs Me About The AISC Code


I don't understand what the problem is.


* 
*   This email was sent to you via Structural Engineers 
*   Association of Southern California (SEAOSC) server. To 
*   subscribe (no fee) or UnSubscribe, please go to:
*
*   http://www.seaint.org/sealist1.asp
*
*   Questions to seaint-ad(--nospam--at)seaint.org. Remember, any email you 
*   send to the list is public domain and may be re-posted 
*   without your permission. Make sure you visit our web 
*   site at: http://www.seaint.org