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.
Okay, here are two "hypothetical" examples that a writer "may" have run into
when working for a government agency. I have not formed a clear opinion on
what a writer's role would be in these situations. Because of the on-going
"to PC or not to PC" discussions, I would be interested in your opinions and
comments on these examples.
Question: Should the writer point out the "un-PC-ness" -- excuse my
language -- of either or both of these examples to the development team
and/or the management?
Example 1:
In a "Programmer's Guide" that is to be used by future maintenance
programmers documenting the database. The database field name is
"indian_tribe" and the field description is "Indian tribe blah-de-dah".
Should the writer tell the database guy that the database field name needs
to be changed because it isn't "Native American"?
Example 2:
On a "button" in an application used by Field Engineers: "Men/Equipment".
Should the writer advise the team that the button name should be changed so
as not to discriminate against women?
Thank you in advance for your opinions.
Rosie Wilcox
rwilc -at- fast -dot- dot -dot- state -dot- az -dot- us
ncrowe -at- primenet -dot- com
Morality is society's rules for the individual's survival; ethics is the
individual's rules for society's survival. - Theodore Sturgeon
