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.
Subject:DISCUSSION: Style Guide Use From:Beth Agnew <bagnew -at- INSYSTEMS -dot- COM> Date:Fri, 14 Nov 1997 13:14:51 -0500
John Posada wrote, in part:
> What I'm getting a in a round-about way is that CMS and all of its
> brothers are only guides. You ARE allowed to do things differently, you
> ARE allowed to use your imagination, and not everything that CMS states
> is law.
> Common, guys, let's show a little imagination and initiative. By the
> time we've reached the qualification level when we are developing our
> company's style guides, we should have seen enough high-quality and low
> quality stuff to make our own decisions on what works and what doesn't.
I agree completely. Sometimes we need guides and rules to help us get
started, but once we've seen what's possible, it's up to us to take those
ideas, add our own, shape the whole thing into something that works for the
type of publication and the audience, and do the best we can. "Technical"
writing doesn't mean that everything has to be, um, by the numbers. There
is indeed room for creativity and imagination. (Just don't sacrifice
accuracy!)
On the other hand, I fully understand shops that have to base their actions
on some authoritative standard. And I'm just as glad I no longer work in a
company that requires some external authority to say bullets or rules or
dot leaders are "okay" before I can use them in a manual.
Being a competent writer is not just knowing exactly where to put the
commas, it's also knowing when to leave them out, for effect.
--Beth
Beth Agnew
Senior Technical Writer, InSystems Technologies Inc.
65 Allstate Parkway, Suite 100 Tel: (905) 513-1400 ext. 280
Markham, Ontario, Canada L3R 9X1 Fax: (905) 513-1419 mailto:bagnew -at- insystems -dot- com Visit us at: http://www.insystems.com