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:Interviewing/getting info From:Marilynne Smith <m -dot- smith182 -at- GENIE -dot- GEIS -dot- COM> Date:Wed, 23 Aug 1995 04:00:00 UTC
>> Do you at least get a feature list from the developers?
The developers should be working from something that states the goal of the
software and its hoped-for features. Now days most companies design the
software first and have a clear idea what their goals are *before* they
begin to code it. If the developer knows what he or she is designing to,
you should be able to find out as well.
As for not sharing . . . you need to develop a better relationship with them
than just eavesdropping. You should be part of the team. Hopefully "one of
the guys". <said tongue in cheek>
Marilynne
m -dot- smith182 -at- genie -dot- geis -dot- com
