As a licensed Professional Engineer I worry about the state of engineering in the US. I feel the word "engineer" is diluted to mean any job that requires technical know-how. Yet there are important ethical considerations if one practices as an engineer. I wish the true engineering professions could have the "Engineer" title differentiated from these other technical professions but it looks like it won't happen anytime soon, if ever. For instance you couldn't practice law or medicine without specific accreditation but for some reason engineering is not differentiated. Sure you can't design a bridge unless you are an accredited Professional Engineer. But the engineer with that title is not differentiated in the marketplace unless the organization knows it.

For those of us who are not Engineers, can you elaborate (or point us to more info) on the Important Ethical Considerations? I've always struggled to explain why programming is not engineering.

Typically there's a subtle difference in courses taken.

For example - at my school Comp Sci were allowed to take physics for physics majors instead of physics for engineers. For both electromagnetic physics and mechanical physics. Typically most engineers are required to take some courses in the some basic courses, ie Dynamics, Statics, and others depending on your major. This all assumes that your ABET accredited. Maybe it's because I don't see an accrediting agency/society. http://en.wikipedia.org/wiki/ABET#Members

Good question. The Engineering profession holds certain code of ethics for the public at large. For instance when you step into a high-rise building, board a cruise ship, or travel across highways they are required to have rigorous testing and design protocol to ensure public safety. I believe NSPE says it best http://www.nspe.org/Ethics/CodeofEthics/index.html

As a programmer who was once an engineer by trade, I would say the difference is that engineering implies manipulation of the pysical sciences, where programming is just logic.

"Just logic" I think really underplays things. That logic ends up in flight control systems, valve control for oil rigs, power grid management, robotics, factory automation, satellites, etc. A lot of software programming has very physical implications.

"Offence, use of term “professional engineer”, etc.

(2) Every person who is not a holder of a licence or a temporary licence and who,

(a) uses the title “professional engineer” or “ingénieur” or an abbreviation or variation thereof as an occupational or business designation;

(a.1) uses the title “engineer” or an abbreviation of that title in a manner that will lead to the belief that the person may engage in the practice of professional engineering;

(b) uses a term, title or description that will lead to the belief that the person may engage in the practice of professional engineering; or

(c) uses a seal that will lead to the belief that the person is a professional engineer,

is guilty of an offence..."

As can be plainly seen, it is perfectly legal to call yourself a software engineer, audio engineer, sanitation engineer, or any other term which isn't holding yourself out to be a licensed professional engineer. The fine is $10,000.

Sort of - the CEAB has in recent years expanded its definition of professional engineering into software engineering also. There are now CEAB-accredited software engineering degrees.

An audio or sanitation engineer is unlikely to run afoul of this, a software engineer is less clear... I've yet to hear of anyone going after software engineers for the term though.