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.
> >From the point of view of a developer working on a new
> project, it would be the requirements/specification for
> the project. From the point of view of a developer
> working with a new tool, i.e., an SDK, it would be the
> user/API doc for the tool. So the answer would depend
> on whether you're being considered for a job documenting
> tools being *used* by the company's developers or tools
> being *written* by them for someone else to use.
>
Because the group creates software tools for developers, and considering
your response, I think the answer I gave was adequate -- the API/SDK (I did
also mention SDK) and the operating system. In this case, the operating system
is a factor, I believe, because the platform in question is not your plain
vanilla Windows or UNIX.
