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.
I think this depends on whether you are creating user documentation or
systems/technical documentation. Each require an understanding of the way
the software works, but to different degrees. I do both, but the majority
of my effort is on user documentation (which you call documenting the GUI).
Katherin King wrote:
> For those of you who document software applications, how much of what
> you do is documenting the GUI and how much of it is documenting the
> underlying structure, the means by which the GUI is implemented? In
> other words, how important is it, do you think, for tech writers to
> understand the inner workings of the software?
>
> Kathy Stanzler
> Technical Writer
> Brooktrout Technology Inc.
> Southborough, MA
> (508) 786-9182
> kking -at- brooktrout -dot- com
>
