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: Bad Documentation and Linux From:"Richard L Hamilton" <dick -at- rlhamilton -dot- net> To:"'TECHWR-L'" <techwr-l -at- lists -dot- techwr-l -dot- com> Date:Mon, 7 Dec 2009 11:24:25 -0700
> From Jon Leer:
>
> The deal is that many developers don't see the point of having a
> non-developer document what they do. Yes, they will add
> comments to the
> code... And that really is all the documentation that is
> necessary (from
> their viewpoint).
>
I agree, though I would argue the best understand documentation and will
work with technical writers. In fact, if I were hiring programmers, I'd
ask some questions to determine their attitude towards writers and
documentation.
Richard Hamilton
---------------------------------
XML Press
XML for Technical Communicators http://xmlpress.net
(970) 231-3624
Are you looking for one documentation tool that does it all? Author,
build, test, and publish your Help files with just one easy-to-use tool.
Try the latest Doc-To-Help 2009 v3 risk-free for 30-days at: http://www.doctohelp.com/
Help & Manual 5: The all-in-one help authoring tool. True single- sourcing --
generate 8 different formats and as many different versions as you need
from just one project. Fast and intuitive. http://www.helpandmanual.com/
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-