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: This too is technical communication From:"Condo, Candis" <ccondo -at- c-cor -dot- com> To:"Dan Goldstein" <DGoldstein -at- riverainmedical -dot- com>, <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Thu, 31 May 2007 14:30:46 -0700
I would be very careful about assuming that QA engineers and developers
do NOT have the customer needs in mind. Or, that only tech writers are
the customer advocates. Come on now. I have worked with many QA
engineers and developers (software types) who do try hard to meet
customer expectations. The very best software is always produced by a
team of developers, QA engineers, tech writers AND tech support
engineers working TOGETHER to produce what the customer needs and wants
in the shortest possible time.
Candis Condo
-----Original Message-----
From: techwr-l-bounces+ccondo=c-cor -dot- com -at- lists -dot- techwr-l -dot- com
[mailto:techwr-l-bounces+ccondo=c-cor -dot- com -at- lists -dot- techwr-l -dot- com] On Behalf
Of Dan Goldstein
Sent: Thursday, May 31, 2007 8:35 AM
To: techwr-l -at- lists -dot- techwr-l -dot- com
Subject: RE: This too is technical communication
I think this speaks to a basic misunderstanding of Quality Assurance.
"Looking for bugs" is only a small part of QA.
Furthermore, software validation (as opposed to verification) focuses
like a laser on the person-computer interface.
> -----Original Message-----
> From: Chris Borokowski
> Sent: Thursday, May 31, 2007 11:17 AM
> To: Troy Klukewich; TECHWR-L
> Subject: Re: This too is technical communication
>
> This is a good point, because it illustrates that more
> than anything else, we are shepherds of the interface
> between user and product and its actual use. No one
> else can afford to think of this; developers write
> code, project managers watch budgets, QA people look
> for bugs. We are looking at the big picture...
>
> We are the only people focused on the person-computer
> interface...
>
This message contains confidential information intended only for the use
of the addressee(s). If you are not the addressee, or the person
responsible for delivering it to the addressee, you are hereby notified
that reading, disseminating, distributing, copying, electronic storing
or the taking of any action in reliance on the contents of this message
is strictly prohibited. If you have received this message by mistake,
please notify us, by replying to the sender, and delete the original
message immediately thereafter. Thank you.
Now shipping: Help & Manual 4 with RoboHelp(r) import! New editor,
full Unicode support. Create help files, web-based help and PDF in up
to 106 languages with Help & Manual: http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as ccondo -at- c-cor -dot- com -dot-
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
Now shipping: Help & Manual 4 with RoboHelp(r) import! New editor,
full Unicode support. Create help files, web-based help and PDF in up
to 106 languages with Help & Manual: http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
