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.
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
> 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.