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.
Eric wrote:---
> Exactly--and I don't think that we're in disagreement at all.
> What you're describing is _exactly_ why the developers put
> a sign reading "testing guru" on my door. That said,
I had a developer, in a meeting, say "Give it to Johnny...he'll break
ANYTHING!"
> I'd say that you're adding value _by_ finding errors and
> conveying the issues to development. The acts of getting
> involved and driving resolution of issues add value,
> and add value that just putting words on paper does not
> add. That's what I'm saying. It's a question of semantics,
> really.
I hope we're not just finding errors, though that happens. By putting
it on paper, the logic (or faulty logic) of a sequence is examined.
By documenting an awkward process, the emporer is shown to have no
clothes. More than once, we've encouraged development to change a
process because once they saw it on paper, they saw how bad it was.
Fixing errors doesn't add value, the errors only took it away.
However, materialy changing the steps that a user performs DOES
increase the value of the product. I'd guess that falls under
usability testing. Does usability testing increase product value? Is
it is possible to write solid documentation about an application that
DOESN'T include this?
> If you want to call the process you describe the act of
> writing, I can go for that. But it's not the typical
> narrow definition of _writing_.
As far as my way not being true writing, I cannot think of any other
way TO write. Are there those that passively write something and if
they see it is difficult to document because it is difficult to
perform, that they don't let anyone know, but just put words on paper?
=====
John Posada, Senior Technical Writer
"I am a bomb disposal expert. If you see me running, try to keep up." mailto:john -at- tdandw -dot- com, 732-259-2874
__________________________________________________
Do You Yahoo!?
Make international calls for as low as $.04/minute with Yahoo! Messenger http://phonecard.yahoo.com/
*** Deva(tm) Tools for Dreamweaver and Deva(tm) Search ***
Build Contents, Indexes, and Search for Web Sites and Help Systems
Available now at http://www.devahelp.com or info -at- devahelp -dot- com
A landmark hotel, one of America's most beautiful cities, and
three and a half days of immersion in the state of the art:
IPCC 01, Oct. 24-27 in Santa Fe. http://ieeepcs.org/2001/
---
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.
