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: John Posada [mailto:jposada01 -at- yahoo -dot- com]
> Anyone with
> half a brain knows that if you are going to write current
> documentation, you need the current version of the software.
Quarter of a brain. Maybe a zero- or negative-brainer. Like I suggested to
someone else, to get the manager's attention on this, you need to get a copy
of Joanne Hackos' book and whack him over the head with it. Or wait for the
paperback version so you can roll it up and shove it up his... <sigh> 1...
2... 3... 4....
> I'm documenting an application and I'm one of the few people
> in the company getting the CD of the link to the network
> install for every build...there was no question (that I know
> of) that I shouldn't.
QA people should get the same thing. Just a few minutes ago I just came out
of the QA lab. This SW developer wanted to show me how his little program
worked. He says he always finds bugs when I'm around. Now I don't "look" for
bugs, but I think any tech writer's thoroughness should reveal bugs in the
process of discovery.