RE: Should software documenters learn to read code?

Subject: RE: Should software documenters learn to read code?
From: "Downing, David" <DavidDowning -at- users -dot- com>
To: "John Posada" <jposada99 -at- gmail -dot- com>
Date: Thu, 12 Feb 2009 09:51:19 -0600

Sp I guess the answer is, "Do it, but only if you know what to do with
it."

-----Original Message-----
From: John Posada [mailto:jposada99 -at- gmail -dot- com]
Sent: Thursday, February 12, 2009 10:46 AM
To: Downing, David
Cc: techwr-l -at- lists -dot- techwr-l -dot- com
Subject: Re: Should software documenters learn to read code?

> Agreed, that's a potential benefit. I'm just thinking there's a
potential danger to go with that benefit.

You mean "Luke..beware of the Darkside."?

Maybe if the tech writer isn't skilled. Those types of writers don't
know the difference between what they should explain and what they
shouldn't, so they try to put on paper everything they know and
everything the developer tells them.

A skilled technical writer puts on paper what they know the user
should know and perhaps more importantly, doesn't include what the
user doesn't need to know. Because the capable writer knows that there
is something that is only of interest to development doesn't mean that
the writer will include it.

That's why companies who hire writers only on rate end up getting the
lowest quality deliverable. What they are getting instead is a
transcription machine that takes lunch and misspells words.

--
John Posada
Senior Technical Writer
NYMetro STC President

Looking for the next gig.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

ComponentOne Doc-To-Help 2009 is your all-in-one authoring and publishing
solution. Author in Doc-To-Help's XML-based editor, Microsoft Word or
HTML and publish to the Web, Help systems or printed manuals.
http://www.doctohelp.com

Help & Manual 5: The complete help authoring tool for individual
authors and teams. Professional power, intuitive interface. Write
once, publish to 8 formats. Multi-user authoring and version control! http://www.helpandmanual.com/

---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-

To unsubscribe send a blank email to
techwr-l-unsubscribe -at- lists -dot- techwr-l -dot- com
or visit http://lists.techwr-l.com/mailman/options/techwr-l/archive%40web.techwr-l.com


To subscribe, send a blank email to techwr-l-join -at- lists -dot- techwr-l -dot- com

Send administrative questions to admin -at- techwr-l -dot- com -dot- Visit
http://www.techwr-l.com/ for more resources and info.

Please move off-topic discussions to the Chat list, at:
http://lists.techwr-l.com/mailman/listinfo/techwr-l-chat


Follow-Ups:

References:
Should software documenters learn to read code?: From: Downing, David
Re: Should software documenters learn to read code?: From: John Posada
RE: Should software documenters learn to read code?: From: Downing, David
Re: Should software documenters learn to read code?: From: John Posada
RE: Should software documenters learn to read code?: From: Downing, David
Re: Should software documenters learn to read code?: From: John Posada

Previous by Author: RE: Should software documenters learn to read code?
Next by Author: Meetings -- ARRGGHHH!!!
Previous by Thread: Re: Should software documenters learn to read code?
Next by Thread: Re: Should software documenters learn to read code?


What this post helpful? Share it with friends and colleagues:


Sponsored Ads