Re: Cooperative Programmers: (Was: Documents Before Products)

Subject: Re: Cooperative Programmers: (Was: Documents Before Products)
From: David C Mason <dcm -at- KPCO -dot- COM>
Date: Thu, 13 Mar 1997 11:40:42 +0000

> BTW, in both cases I told the programmers that my primary job was to
> document the program, not determine how it should work. But if I felt
> I could contribute to the usability or interface design, I gave my
> opinion.
>
> Anybody else encountered this situation?
>
I had a very similar experience in which I made off-the-cuff comments about
interface to a manager while on a contract job. I was then hired to do
tech-writing AND interface design. I think it behooves us to use our
expertise in the flow of work to help out programmers.


David Mason

TECHWR-L (Technical Communication) List Information: To send a message
to 2500+ readers, e-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send commands
to LISTSERV -at- LISTSERV -dot- OKSTATE -dot- EDU (e.g. HELP or SIGNOFF TECHWR-L).
Search the archives at http://www.documentation.com/ or search and
browse the archives at http://listserv.okstate.edu/archives/techwr-l.html


Previous by Author: Re: quality control -suggestions please
Next by Author: keyboards
Previous by Thread: Re: Parentheses with other Punctuation - Question
Next by Thread: Cooperative Programmers: (Was: Documents Before Products)


What this post helpful? Share it with friends and colleagues:

Sponsored Ads


Sponsored Ads