Skip to main content Accessibility help
×
Hostname: page-component-848d4c4894-8bljj Total loading time: 0 Render date: 2024-07-07T23:34:52.110Z Has data issue: false hasContentIssue false

A

Published online by Cambridge University Press:  25 October 2011

Henry Petroski
Affiliation:
Duke University, North Carolina
Get access

Summary

abbreviations. As frequently as engineers find themselves using the words engineer and engineering, they do not appear to have agreed on any single standard or official shorthand for the words. Among the abbreviations I have seen used are egr., eng., engr., eng'r., and engng. – none of which is especially mellifluous or, in isolation, unambiguous. Abbreviations are not meant to be pronounced as such, however, and as long as the context is clear there should be little need to worry about them being misunderstood. Even so, the arrangement of the letters in these abbreviations is not especially typographically graceful, and situations can arise where confusion might result, as in a university setting when a course number is designated Eng. 101. Is this Engineering 101 or English 101 or Energy 101? Engineers dislike ambiguity, and so the imprecision of an abbreviation for our own profession is annoying, to say the least.

It is apparently this aversion to ambiguity that has led engineers to introduce less-than-logical abbreviations for themselves. And it may well have been the potential confusion over what “eng.” designates (engine, engineer, engineering, English, engrave, etc.) that led to the introduction of the unconventional, unpronounceable, and ungraceful abbreviation egr. for engineer, and sometimes its natural extension egrg. or egrng. for engineering. Although many common abbreviations have multiple meanings, the context can be expected to make clear which one is intended. Unfortunately, the words engine, engineer, and engineering often occur in the very same context.

Type
Chapter
Information
An Engineer's Alphabet
Gleanings from the Softer Side of a Profession
, pp. 1 - 16
Publisher: Cambridge University Press
Print publication year: 2011

Access options

Get access to the full version of this content by using one of the access options below. (Log in options will check for institutional or personal access. Content may require purchase if you do not have access.)

Save book to Kindle

To save this book to your Kindle, first ensure coreplatform@cambridge.org is added to your Approved Personal Document E-mail List under your Personal Document Settings on the Manage Your Content and Devices page of your Amazon account. Then enter the ‘name’ part of your Kindle email address below. Find out more about saving to your Kindle.

Note you can select to save to either the @free.kindle.com or @kindle.com variations. ‘@free.kindle.com’ emails are free but can only be saved to your device when it is connected to wi-fi. ‘@kindle.com’ emails can be delivered even when you are not connected to wi-fi, but note that service fees apply.

Find out more about the Kindle Personal Document Service.

  • A
  • Henry Petroski, Duke University, North Carolina
  • Book: An Engineer's Alphabet
  • Online publication: 25 October 2011
  • Chapter DOI: https://doi.org/10.1017/CBO9781139057516.003
Available formats
×

Save book to Dropbox

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Dropbox.

  • A
  • Henry Petroski, Duke University, North Carolina
  • Book: An Engineer's Alphabet
  • Online publication: 25 October 2011
  • Chapter DOI: https://doi.org/10.1017/CBO9781139057516.003
Available formats
×

Save book to Google Drive

To save content items to your account, please confirm that you agree to abide by our usage policies. If this is the first time you use this feature, you will be asked to authorise Cambridge Core to connect with your account. Find out more about saving content to Google Drive.

  • A
  • Henry Petroski, Duke University, North Carolina
  • Book: An Engineer's Alphabet
  • Online publication: 25 October 2011
  • Chapter DOI: https://doi.org/10.1017/CBO9781139057516.003
Available formats
×