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.
And expecting developers to like or value spending their time doing
documentation is like expecting the cat to be happy when you put it in
the bath water. The agile modeling site is clearly a software
development methodology written by developers, not a site about tech
writing, so I can't see much reason to get offended. Why do we care if
the developers want to do documentation? I actually thought the author
did see some value in technical writers--he did suggest hiring some. He
just doesn't want to BE one. Good! More work for us.
I'm still curious: are lots of tech writers being employed writing the
kind of project documentation this site describes as the documents that
factor into agile programming? If so, are they largely more traditional
development projects, or moving toward rapid development (pick your
flavor)?
Lisa
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Attention ForeHelp and Doc-to-Help Users! Upgrade your existing product to
RoboHelp for FREE, through January 15th. RoboHelp can import your existing
Help projects! Learn how else RoboHelp can benefit you. www.ehelp.com/techwr
---
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.
