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.
Re: Should software documenters learn to read code?
Subject:Re: Should software documenters learn to read code? From:Deb McNally <tig -dot- techwriter -at- gmail -dot- com> To:"Downing, David" <DavidDowning -at- users -dot- com> Date:Fri, 13 Feb 2009 06:54:27 -0500
I would have to disagree. I have been able to read (and write) code
for years. It definitely didn't change the way I think. What it did do
is make it so that I am able to understand what the programmers are
saying when they get stuck in 'programmer speak'. This has made me an
asset to the companies I have worked for because I can interpret and
explain to others.
Reading code is also a great item to have on your resume.
Deb
Sent from my iPhone
On Feb 12, 2009, at 10:03 AM, "Downing, David"
<DavidDowning -at- users -dot- com> wrote:
> Should technical writers who do software documentation -- which is
> most
> of us -- learn to read the actual code of the software they're
> documentation? Of course, on general principles, the more you know the
> better. And if you learned the programming language on your own time,
> the question of whether you should be spending your on-the-clock time
> doing so wouldn't be an issue.
>
> But there is a danger. One reason programmers tend to make bad
> documenters is that they think in terms of the mechanics of the
> program,
> rather than in terms of the tasks the end user needs to perform. I
> technical writer who starts reading code might start thinking this way
> as well.
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> 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 tig -dot- techwriter -at- gmail -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/tig.techwriter%40gmail.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
>
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
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-