TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
Subject:typos in resumes From:David Hailey <FAHAILEY -at- WPO -dot- HASS -dot- USU -dot- EDU> Date:Fri, 16 May 1997 14:23:59 -0600
We might also remember that typos are not always typos. Many of the
"prescriptions" in style guides are not prescriptions at all. They are often
merely suggestions or recommendations--often stated as, "Tradition holds that.
. ." Furthermore, there are rules that we tend to forget as a group. For
example, "Use a comma when necessary to avoid ambiguity." I have often
received "gigs" from VPs and technical editors that have forgotten or never
knew that rule. I once received a scathing review from someone who used an
MLA style guide to attack my APA style.
I have often seen people in this group not know a rule (so they ask the
group). But I have also seen people in this group reject a rule that is
clearly written but is still nonsense--remember the 12:00M strand?
I would hate to tell an applicant that I rejected him/her because of typos
only to find that I was wrong or that the "typos" represented aesthetic
differences of opinion.
For what it's worth.
Assistant Prof etc. . .
Utah State University
fahailey -at- wpo -dot- hass -dot- usu -dot- edu