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:Re: Writing vs. Testing From:Mary Choy <mchoy -at- SIRIUS -dot- COM> Date:Fri, 21 May 1999 17:19:18 +0000
I've been contract tech writing for about 4 months, and have had a few start-
ups as my clients. Each of them has been a "tech writing" job, but in order to
get something to write about, I've had to use the product. That means, given
there are no written specs and very little if ANY QA staff, testing the alphs,
reporting bugs, redesigning UI. I've never been given a test script, test plan,
test cases, or even solid and consistent test data (you lucky dog!). It's been
fun for me, though. I really don't see it as mind-numbing, because I get to
contribute to improving the end product, and get to see it take shape, so when
I actually get down to writing, it writes itself (practically :) ).
I don't know if this is typical elsewhere, but in the Bay Area (san fran) at
start-ups, it seems to be.