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.
React like a program that has gotten incorrect input: give another copy of the same first draft to the developer with the same instructions. Maybe the developer will get it the second time. If not . . .
Or, when you are asked to write a document about a product this developer has created, instead add a bunch of spaghetti code to his code, and ask him how it feels.
Or, maybe ask the developer why he didn't do a technical edit. If you want to be obnoxious, you may also add a question as to why he wasted company time doing someone for which he clearly is unqualified.
Seriously. . .
It is a hard situation. Usually, when someone is off task you can soften the correction by complementing what they did well even though it wasn't what was called for. But in your case, what the developer did was clearly inferior, nothing to compliment. Perhaps praise his concern for the quality of the prose, but then point out that the company can not afford for him to spend his time writing--but really needs his technical input.
Leonard Porrello
ES&S
Engineering Scribe
----------
From: leona.magee-dupree
Sent: Thursday, December 17, 1998 10:05 AM
To: TECHWR-L; LCPORREL
Subject: Developers
I gave a copy of instructions to a developer and the developer ignored the
instructions and changed the sentences from active to passive. The
developer tried to edit the documentation. What does a technical writer
have to do to get feedback about the accuracy of a document and not "tid
bits" of how to write from someone who does not know how to write? Why do
developers do this? How should we react?