Re: Post on Technical Writing vs. Technical Communication

Subject: Re: Post on Technical Writing vs. Technical Communication
From: "Peter Neilson" <neilson -at- windstream -dot- net>
To: "Gene Kim-Eng" <techwr -at- genek -dot- com>
Date: Wed, 04 Apr 2012 18:15:57 -0400

Here's how it is in North Carolina :-

=======================================================
North Carolina General Statutes  89C-23 Unlawful to practice engineering or land surveying without licensure; unlawful use of title or terms; penalties; Attorney General to be legal adviser

Any person who shall practice, or offer to practice, engineering or land surveying in this State without first being licensed in accordance with the provisions of this Chapter, or any person, firm, partnership, organization, association, corporation, or other entity using or employing the words "engineer" or "engineering" or "professional engineer" or "professional engineering" or "land surveyor" or "land surveying," or any modification or derivative of those words in its name or form of business or activity except as licensed under this Chapter or in pursuit of activities exempted by this Chapter ...
=======================================================

You cannot call yourself an engineer in NC without a license.

On Wed, 04 Apr 2012 18:03:50 -0400, Gene Kim-Eng <techwr -at- genek -dot- com> wrote:

I don't know of any state in the US where that's the case, and nationwide
only 20% or so of all people working with the title of "Engineer" have a PE
license.

"Professional Engineer" does require a license in all 50 states (and, I
think, all Canadian provinces)..

Gene Kim-Eng


On Wed, Apr 4, 2012 at 2:38 PM, Peter Neilson <neilson -at- windstream -dot- net>wrote:

In some states it is illegal to use the job title "Engineer" unless you
are a licensed professional engineer.

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Create and publish documentation through multiple channels with Doc-To-Help. Choose your authoring formats and get any output you may need.

Try Doc-To-Help, now with MS SharePoint integration, free for 30-days.

http://bit.ly/doc-to-help

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
To unsubscribe send a blank email to
techwr-l-leave -at- lists -dot- techwr-l -dot- com


Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
http://www.techwhirl.com/email-discussion-groups/ for more resources and info.

Looking for articles on Technical Communications? Head over to our online magazine at http://techwhirl.com

Looking for the archived Techwr-l email discussions? Search our public email archives @ http://techwr-l.com/archives

Follow-Ups:

References:
Post on Technical Writing vs. Technical Communication: From: Cardimon, Craig
RE: Post on Technical Writing vs. Technical Communication: From: Dan Goldstein
RE: Post on Technical Writing vs. Technical Communication: From: Cardimon, Craig
RE: Post on Technical Writing vs. Technical Communication: From: Dan Goldstein
RE: Post on Technical Writing vs. Technical Communication: From: Steve Janoff (non-Celgene)
RE: Post on Technical Writing vs. Technical Communication: From: Cardimon, Craig
RE: Post on Technical Writing vs. Technical Communication: From: Steve Janoff (non-Celgene)
Re: Post on Technical Writing vs. Technical Communication: From: Peter Neilson
Re: Post on Technical Writing vs. Technical Communication: From: Gene Kim-Eng

Previous by Author: Re: Post on Technical Writing vs. Technical Communication
Next by Author: Re: Post on Technical Writing vs. Technical Communication
Previous by Thread: Re: Post on Technical Writing vs. Technical Communication
Next by Thread: RE: Post on Technical Writing vs. Technical Communication


What this post helpful? Share it with friends and colleagues:

Sponsored Ads


Sponsored Ads