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:Re: Can software have human attributes? From:Janice Gelb <janiceg -at- marvin -dot- eng -dot- sun -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Wed, 25 Jul 2001 13:49:04 -0700 (PDT)
Diane Backus <DBackus -at- DocByDesign -dot- com> wrote:
>
> A corporate style guide reads:
> "Avoid attributing human actions to inanimate objects, particularly
> software. Example: Instead of 'The program sits and waits for the next
> active result in the queue', write 'The program polls the queue for the next
> active result.'"
> Several developers have disagreed with this since the style guide was
> published. What is the general acceptance level for attributing human
> actions to software? If anyone can cite a source (Microsoft style, perhaps),
> that would be helpful.
>
Sun's style guide also discourages anthropomorphisms: they
encourage the reader to think that the computer can make
decisions beyond what they are programmed to do. However,
we do allow slight anthropomorphisms that help the reader
understand computer activity by comparing it to behavior
a person might do: the system "listening" to a network,
for example.
I think "sits and waits" might be right on the edge for
me, especially the "sits" part. OTOH, I don't think
anyone would disagree that the following (which I saw
in a manual that I edited) definitely crosses the line:
"These hardware drivers must be aware of the restrictions
on page 237."
Not only did the drivers have to be self-aware, they also
had to be able to read and turn pages :->
*** Deva(tm) Tools for Dreamweaver and Deva(tm) Search ***
Build Contents, Indexes, and Search for Web Sites and Help Systems
Available now at http://www.devahelp.com or info -at- devahelp -dot- com
Learn about tools and technologies for user assistance developers at
The Help Technology Conference, August 21-24 in Boston, MA
Details and online registration at http://www.SolutionsEvents.com
---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.