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.
Kris Olberg, replying to a message by John Brinegar, writes:
<What makes you think that a production department
<cannot do the job as well as you? This is exactly why
<I think dilution of job skills is bad; the production people
<have, in many writer's eyes, suddenly become unskilled,
<unnecessary, and not able to do the job as well as the writer.
I can cite one case in which the production department of a large, New
York publishing house was unable to do the job as well as the writer.
In 1991 a friend and I wrote a book on Novell's NetWare v2.2 for
John Wiley & Sons. It had several tables of options to include with
command sequences that could have been set within the margins of the
step lists that included the tables. I fought and lost regarding the layout
we thought would be clearest for the readers. Each table was set
margin-to-margin, with the labels of the option categories set indented
between each set of tables, so that (in my opinion) the information got
lost. (I know this is hard to visualize). Anyway, everybody I ever
talked to agreed it was ugly and made the hierarchy of information
Technical writers today are also designers and layout artists. It goes
with the job. The job has changed, for better or worse.
mandrews -at- novell -dot- com