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:Chuck Banks <chuck -at- ASL -dot- DL -dot- NEC -dot- COM> Date:Tue, 12 Oct 1993 10:56:36 CDT
Your experience reminded me of the phrase used by some
mathematics text authors "...it is intuitively obvious that ..."
This phrase usually appeared in informal proofs of mathematical
theorems. On occasion, the step succeeding the assertion was obvious.
More often, however, the phrase was used to bypass a laborous proof or
discussion of such a proof.
In teaching texts, the phrase served a useful purpose.
Temporarily bypassing a proof to explore the "big picture." Later,
the bypassed proof was posed as a student exercise.
So, sometimes the phrase was correct, sometimes a labor saver
for the writer, and sometimes a teaching aid.
In technical writing, I agree, the terms obvious and obviously
are time wasters or sops to the writer's ego. If something is truely
obvious, show it in a figure or omit it. If something is not obvious,
don't puff yourself up by saying it is. Either way, obvious and
obviously are, to me, irritants.
__ ________ ______
|\\ | || // Chuck Banks
| \\ | ||_______ || Senior Technical Writer
| \\ | || || NEC America, Inc.
| \\| \\______ \\______ E-Mail: chuck -at- asl -dot- dl -dot- nec -dot- com
America, Incorporated CompuServe: 72520,411