How does a code of ethics achieve these goals?

First, a code of ethics helps create an environment within a profession where ethical behavior is the norm. It also serves as a guide or reminder of how to act in specifi c situations. A code of ethics can also be used to bolster an individual’s position with regard to a certain activity: The code provides a little backup for an individual who is being pressured by a superior to behave unethically. A code of ethics can also bolster the individual’s position by indi- cating that there is a collective sense of correct behavior; there is strength in num- bers. Finally, a code of ethics can indicate to others that the profession is seriously concerned about responsible, professional conduct [ Harris, Pritchard, and Rabins, 2000 ]. A code of ethics, however, should not be used as “window dressing,” an attempt by an organization to appear to be committed to ethical behavior when it really is not.

2.3.2 Objections to Codes Although codes of ethics are widely used by many organizations, including engi- neering societies, there are many objections to codes of ethics, specifi cally as they apply to engineering practice. First, as mentioned previously, relatively few practic- ing engineers are members of professional societies and so don’t necessarily feel compelled to abide by their codes. Many engineers who are members of profes- sional societies are not aware of the existence of the society’s code, or if they are aware of it, they have never read it. Even among engineers who know about their society’s code, consultation of the code is rare. There are also objections that the engineering codes often have internal confl icts, but don’t give a method for resolv- ing the confl ict. Finally, codes can be coercive: They foster ethical behavior with a

26 2.3 Codes of Ethics

stick rather than with a carrot [ Harris, Pritchard, and Rabins, 2000 ]. Despite these objections, codes are in widespread use today and are generally thought to serve a useful function.

2.3.3 Codes of the Engineering Societies Before examining professional codes in more detail, it might be instructive to look briefly at the history of the engineering codes of ethics. Professional engineering societies in the United States began to be organized in the late 19th century. As these societies matured, many of them created codes of ethics to guide practicing engineers.

Early in the 20th century, these codes were mostly concerned with issues of how to conduct business. For example, many early codes had clauses forbidding advertising of services or prohibiting competitive bidding by engineers for design projects. Codes also spelled out the duties that engineers had toward their employers. Relatively less emphasis than today was given to issues of ser- vice to the public and safety. This imbalance has changed greatly in recent dec- ades as public perceptions and concerns about the safety of engineered products and devices have changed. Now, most codes emphasize commitments to safety, public health, and even environmental protection as the most important duties of the engineer.

2.3.4 A Closer Look at Two Codes of Ethics Having looked at some ideas about what codes of ethics are and how they function, let’s look more closely at two codes of ethics: the codes of the IEEE and the NSPE. Although these codes have some common content, the structures of the codes are very different.

The IEEE code is short and deals in generalities, whereas the NSPE code is much longer and more detailed. An explanation of these differences is rooted in the philosophy of the authors of these codes. A short code that is lacking in detail is more likely to be read by members of the society than is a longer code. A short code is also more understandable. It articulates general principles and truly functions as a framework for ethical decision making, as described previously.

A longer code, such as the NSPE code, has the advantage of being more explicit and is thus able to cover more ground. It leaves less to the imagination of the indi- vidual and therefore is more useful for application to specifi c cases. The length of the code, however, makes it less likely to be read and thoroughly understood by most engineers.