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.
> I've been asked (as part of a reorganization my department is currently
> undergoing) to explore ways in which a documentation department can use an
> engineer on its staff. I know that quality validation is one topic that has
> been discussed on the list recently, and that's certainly a job an engineer
> working for a documentation department could do.
> Does anyone have other ideas?
> Judith Hammeran
> The MacNeal-Schwendler Corp.
> judith -dot- hammeran -at- macsch -dot- com
I'm curious - Does your documentation dept. have any engineering writers
already? If not, then that's probably what your senior managers are trying
to tell you ;-) If you have engineers (or technologists) already,
perhaps you would benefit by doing your own validation and verification.
There's nothing like an engineer with no technical communication training
to mess up your project!
Bernie (engineer & tech. communicator) ;-)
_/_/_/_/ _/_/_/_/_/ _/_/_/_/ "Caesar had perished from the world of men
_/ _/ _/ _/ _/ _/ Had not his sword been rescued by his pen."
_/_/_/_/ _/ _/ _/ _/_/_/_/