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:Re: Responsible use of Obviously From:Margaret Gerard <margaret -at- TOSHIBA -dot- TIC -dot- OZ -dot- AU> Date:Wed, 13 Oct 1993 09:39:45 EST
Steve,
The use of "obviously" as you describe would be edited out of documents prepared
here because it is presumptious and patronizing. It presumes that the reader
shares the writer's opinion of the subsequent statement while at the same time
implying that the writer considers that the obvious must be stated - is the
reader stupid?
I also think it gives a pompous tone to the work. This type of problem can be
very difficult to eradicate.
An interesting problem I have noticed in work drafted by software engineers is
the relentless use of "then" after every "if" as though English must follow the
rules of the programming language they are using! This gives a really plodding
effect.
