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.
>John, are you supposing we technical writers
>know how to code? Personally I don't think
>that's relevant. So when someone
Dan...I was just thinking about this further.
For technical writers who are involved in situations where application
development is the major effort, what's wrong with knowing something
about code.
Not to the level that a developer knows (though there is nothing WRONG
with this), but if you are documenting relational databases, what's
wrong with knowing how to create a simple three line SQL statement, or
if you are documenting application written in VB, maybe knowing a little
about controls and properties?
