RE: Should software documenters learn to read code?

Subject: RE: Should software documenters learn to read code?
From: "Victoria Wroblewski" <victoria -dot- wroblewski -at- eagletest -dot- com>
To: "Downing, David" <DavidDowning -at- users -dot- com>, <techwr-l -at- lists -dot- techwr-l -dot- com>
Date: Fri, 13 Feb 2009 09:58:07 -0600

-----Original Message-----
From: Downing, David
Sent: Thursday, February 12, 2009 9:04 AM
Subject: Should software documenters learn to read code?

>(A) technical writer who starts reading code might start thinking this
way
>as well.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

It all depends. If you look at code as a programming language, it's a
lot like any other language. You may learn enough Italian for your trip
to Italy so you can veer away from your English-speaking tour group and
walk around the market or go to a restaurant without being totally lost,
but there is a big difference between being able to find out where the
nearest bathroom is and being fluent in a language.

Being able to look at code and understand some of it is a useful skill,
but you don't need to become immersed in the World of Code. And I think
you can easily read code and not go down the path of starting to think
of the mechanics of a program - you can stay a lot more detached from
the mechanics of it when it takes you a few minutes to say "Oh, that's
how they did 'that'!" to yourself vs. being one of the team that put six
months of 9-10 hour days into figuring how to get the code to do "that."


- V

**This transmission may contain information that is privileged, confidential and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you.**
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

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


References:
Should software documenters learn to read code?: From: Downing, David

Previous by Author: RE: Meetings -- ARRGGHHH!!!
Next by Author: RE: The Limits of Training
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


Sponsored Ads