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.
Betsy Perry <betsyp -at- VNET -dot- NET> wrote:
> o Show them that your interruptions, far from slowing them down, can
> actually save developer time by pointing out inconsistencies in the
> design before they become bugs in the code.
I also point out that my job on the team is to communicate the genius of what
the developers create to the end users. After this bit of flattery, I then give the
developers a choice. They can explain their work once to me and I'll write it up
for the end users, or they can answer the phones when the end users call and
they can explain it themselves. Either way the users MUST be told about what
the product does. I've never had a developer decide on the phone support option,
even facetiously. Once I explain it this way, they are most willing to tell me
what they are creating.
--- John Bell
johnb -at- c-stone -dot- com
TECHWR-L List Information
To send a message about technical communication to 2500+ list readers,
E-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send administrative commands
ALL other questions or problems concerning the list
should go to the listowner, Eric Ray, at ejray -at- ionet -dot- net -dot-
