Need a book? Engineering books recommendations...

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

RE: View proposed ACI 318 revisions

[Subject Prev][Subject Next][Thread Prev][Thread Next]
Talk to your government. There is nothing stopping governments from writing their own codes. In fact, that is kind what used to be a long time ago...but then people started working in broader geographic areas and they did not want to have to deal with dozens of different codes. Still, there is nothing stopping the federal government from writing a National Building Code (the Constitution may stop the federal government from forcing that code on all the states...so called "states' rights" and all), except all the people who don't want to pay taxes for things that benefit us all but most don't consider a priority (everyone sure likes a nice, well built road, but don't seem to want to pay the taxes that support the building of those roads and other such things). Anyways, good luck on getting Congress to agree to do that when they can seem to do the more visiable things like immigration and healthcare.

Regards,

Scott
Adrian, MI

On Fri, 6 Jul 2007, Donald Bruckman wrote:


This all gets back to our discussion last month about code costs. When you
think about it, the free enterprise approach to code writing, (i.e. private
companies like ICC doing code writing) is really antithetical to true
quality engineering.  It's the equivalent of Apple vs Microsoft, open code
vs proprietary code.  How many engineers would just choose to ignore some
obscure and minor requirement hidden in a $2000 code they knew would have
minimal effect on the overall design?


-----Original Message-----
From: Christopher Wright [mailto:chrisw(--nospam--at)skypoint.com]
Sent: Friday, July 06, 2007 10:34 AM
To: seaint(--nospam--at)seaint.org
Subject: Re: View proposed ACI 318 revisions


On Jul 6, 2007, at 11:19 AM, Garner, Robert wrote:

With Codes becoming available electronically, how about a
consortium of a group of engineers that collectively buy and
"share" the codes electronically.  Only one engineer could view any
one of the codes at a time but with a good share schedule set up,
it might work.  As it is now, the AWS code is not in my budget so I
can't see it anytime.  Being able to at least see it between 4:00
and 6:00 pm on Wednesdays and Thursdays is better than nothing.
Sort of a Code "time share".
I think this is a damn good idea. Something like it might be a reason
to keep up membership in technical societies. I don't know how the
ASCE or the ACI fares these days, but the ASME is falling on
increasingly harder times, primarily because there's fewer reasons to
belong. Students flock in because it looks good on a resume and the
dues aren't very high, but membership by experienced engineers tapers
off really fast, except for dyed-in-the-wool joiners.

One of the things they should do is offer on-line Code access to
members as a perk of membership. Full purchase of all umpteen volumes
of the Boiler Code is close to $2000. and the codes are re-issued
every 3 years. There are good reasons for some people to have
personal copies, but many of us can't possibly justify 2 grand every
three years on the off chance that we might need something in some
obscure section. The ASME, like every other society, makes pretty
good money in the publishing business, but they need to look further
than the end of their collective noses when it comes to member
benefits. Code access, even limited to so many log-ons a month, would
be a good one.

Christopher Wright P.E. |"They couldn't hit an elephant at
chrisw(--nospam--at)skypoint.com   | this distance" (last words of Gen.
.......................................| John Sedgwick, Spotsylvania
1864)
http://www.skypoint.com/~chrisw/



******* ****** ******* ******** ******* ******* ******* ***
*   Read list FAQ at: http://www.seaint.org/list_FAQ.asp
*
*   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
******* ****** ****** ****** ******* ****** ****** ********


******* ****** ******* ******** ******* ******* ******* ***
*   Read list FAQ at: http://www.seaint.org/list_FAQ.asp
*
*   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
******* ****** ****** ****** ******* ****** ****** ********




******* ****** ******* ******** ******* ******* ******* ***
*   Read list FAQ at: http://www.seaint.org/list_FAQ.asp
* * 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 ******* ****** ****** ****** ******* ****** ****** ********