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.
> -----Original Message-----
> From: Tom Murrell [mailto:trmurrell -at- yahoo -dot- com]
> Subject: Re: Imperatives or not?
> Regardless of whether or not I would do it the way you are
> suggesting, Sierra,
> I would say to your engineer: "Me writer. Me make grammar choices. You
> engineer. You review for TECHNICAL accuracy and completeness only."
So if engineers find typos, they shouldn't mention them? If they think a
sentence might be confusing, they shouldn't mention it? If they think this
section should come before that one, they shouldn't mention it?
I don't think so. I treat my docs as (at least somewhat) more collaborative.
Just as I would mention something about the program or hardware that I
thought could use improvement, I would also hope that the engineers could do
the same for me. Not that I'll necessarily follow their advice, but I
wouldn't discourage it based on their job title.
All communication contained in this e-mail is entirely my own and is not
necessarily endorsed by my co-workers or employer.