Need a book? Engineering books recommendations...
Fwd: Re: malfeasance sanctions (was: code minimums)[Subject Prev][Subject Next][Thread Prev][Thread Next]
- To: addseaoc(--nospam--at)euken.com
- Subject: Fwd: Re: malfeasance sanctions (was: code minimums)
- From: rlewis(--nospam--at)techteam.org (Richard Lewis)
- Date: 30 Jul 1997 14:47:26 GMT
>If the range >of transgressions that licensees in my state are successfully disciplined for >are representive, very few of those 20 to 40 cases each year Minnesota will >be on charges related to inadequate or incompetent design services, or >rubberstamping. Actually, most of the ones I recollect are for just that--practicing out of area of expertise, plan stamping, advertising services not qualified for (presumably this latter includes actually performing such services). Florida has some specific rules about fire sprinkler design, and installers get gigged for providing engineering services. I don't know what that sort of this is called in California, but I think design of emergency systems is no more a matter for hackery than aseismic structural design. >charges of practicing outside of area(s) of competence may more >frequent due to greater temptations to engage in figureheading or >rubberstamping. These mal/misfeasance cases and cases involving >procedural/statutory violations are beside the point, Nonsense. If I strolled up and offered to provide a reinforced concrete design, I should have my butt kicked just as hard in California as Minnesota, since I'm not competent to do it. >Progress in achieving the common goals of the engineering profession - > compliance with the spirit of our licensing laws and canons of ethics - >won't start until a significant percentage of us voluntarily subscribe to >them. We've already voluntarily subscribed to them. All 100% of us. Make all the excuses you like, but holding ourselves individually accountable for professional actions is the guts of a profession. And if we can't hold ourselves accountable, with laws that have teeth, who else can? Christopher Wright P.E. |"They couldn't hit an elephant from chrisw(--nospam--at)skypoint.com | this distance" (last words of Gen. ___________________________| John Sedgwick, Spotsylvania 1864) http://www.skypoint.com/subscribers/chrisw --- Internet Message Header Follows --- Received: from server1.seaoc.org (bqe.com [188.8.131.52]) by host1.texramp.net (8.8.5/8.8.5) with SMTP id QAA26678 for <rlewis(--nospam--at)techteam.org>; Sat, 1 Mar 1997 16:59:32 -0600 (CST) Received: from skypoint.com by server1.seaoc.org (NTList 3.02.10) id ra005113; Sat, 1 Mar 1997 14:58:01 -0800 Received: from [184.108.40.206](really [220.127.116.11]) by mirage.skypoint.com via smtpd with smtp id <m0w0xgr-0004GuC(--nospam--at)mirage.skypoint.com> for <seaoc(--nospam--at)seaoc.org>; Sat, 1 Mar 1997 16:55:41 -0600 (CST) (Smail-3.2 1996-Jul-4 #4 built 1997-Feb-13) Message-Id: <m0w0xgr-0004GuC(--nospam--at)mirage.skypoint.com> Subject: Re:malfeasance sanctions (was: code minimums) Date: Sat, 1 Mar 97 17:02:34 -0600 X-Sender: seaoc-ad(--nospam--at)seaoc.org x-mailer: Claris Emailer 1.1 From: Christopher Wright <chrisw(--nospam--at)skypoint.com> To: "SEAOC Newsletter" <seaoc(--nospam--at)seaoc.org> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Reply-To: seaoc(--nospam--at)seaoc.org Error-To: seaoc-ad(--nospam--at)seaoc.org X-Loop: seaoc(--nospam--at)seaoc.org X-Info: [SEAOC] Owner: seaoc-ad(--nospam--at)seaoc.org X-POP3-Rcpt: seaoc-ad(--nospam--at)seaoc.org Precedence: list X-ListMember: rlewis(--nospam--at)techteam.org [seaoc(--nospam--at)seaoc.org] __________________________________________________ Richard Lewis, P.E. Missionary TECH Team rlewis(--nospam--at)techteam.org The service mission like-minded Christian organizations may turn to for technical assistance and know-how.
- Prev by Subject: FW: MAILER-DAEMON(--nospam--at)efdswest.navfac.navy.mil:
- Next by Subject: Masonry f'm
- Previous by thread: Fwd: Re: Ongoing discussion of professional practice
- Next by thread: Fwd: Hyatt walkway