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.
And then there was the "Warning: this beta update fixes a Real Bad Problem
- update now, don't run the beta you have" sheet. Got bounced back and
forth for days, developers wanted it to look scarier, marketing wanted it
more reassuring. Half an hour to write, several days to revise, and in the
end it was, down to the word, punctuation mark, and layout, identical to
the results of the half hour.
Meanwhile, at the beta sites... Well, actually, nothing happened. There
were only a few beta sites and it took an obscure and unlikely sequence of
events to trigger the problem. The potential problem was discovered and
fixed by a very alert and customer-focused programmer, and never, as far as
I know, happened.
Mike Huber, celebrating 2750 years of decline, and not speaking for anybody
Mike -dot- huber -at- software -dot- rockwell -dot- com
Grammar and spelling are tools to be used in moderation.
From: Melonie Holliman [SMTP:mrh -at- abmdata -dot- com]
Sent: Thursday, April 24, 1997 5:01 AM
To: TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU
Subject: Re: Job Posting: Technical Marketing Writer
It did get me thinking about the marketing vs. engineering
thing, though. Does anyone else feel pulled between the
two? I feel like there is a war going on in my company.
Is this normal for the software development process?