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.
Harry Hager suggests <<Forget about the "display" part... I want to talk
about the "will" part. How many of you use future tense in your technical
writing? I've always avoided using future tense in technical writing.>>
I try to avoid "will" unless I'm really talking about something that belongs
in the future and has a reasonably definite time when the event will occur
(e.g., "Microsoft Reminder will send e-mail on that future date to remind
you to...", "this process will take at least 5 minutes, and possibly up to a
maximum of XX hours"). The problem with using the unadorned future "will" is
that it provides no clear indication of _when_ the future event will happen,
and draws the reader out of the present (what I'm doing now) into a
different tense (what happens in the future), then back to the present to
continue with the present (next step that I'm doing).* And worse yet, system
crashes, bugs, and other "features" often mean that _will_ becomes _will
* This leads to temporal dislocation, as all science fiction writers know.
Not a good thing.
<<The only reason I'm writing this is that nobody else has mentioned it so
far. This surprises me.>>
True enough, but it has been discussed several times over the past 8 years;
check the archives. I'm as guilty as anyone about answering the direct
question and not exploring whether it's the correct question to be asking in
the first place.
<<Why use present tense only? When a user is reading a set of instructions
and performing a set of instructions, each step is occurring in the present
tense as related to the user.>>
That certainly fits my experience. Though in retrospect, it occurs to me
that we still have the same problem with system crashes etc.: our
instructions blithely assume the entire process works smoothly, but when
"life happens", the reader is still left feeling cheated. Not a huge
problem, but still...
<<I've always considered this (using present tense) as one of the basic
rules of technical writing. Am I wrong?>>
Yes, provided that (as you and I both noted), you recognize that any rule
has clear exceptions, such as the ones I pointed out earlier in this message
and your own observation that there are some cases where future tense is
appropriate. When we start applying rules blindly, we stop thinking about
whether the rules are always appropriate.
"Quebits took the art of manual writing to such extremes [that] the first
human scholars who'd tried to decipher their written language had spent a
lifetime working through what they hoped would be a definitive piece of
Quebit culture. No one was quite ready to say it wasn't, but the huge
ancient text had proved to be a manual for installing a sewage system within
a city."--Julie Czerneda, "Changing Vision"
Sponsored by SOLUTIONS, Conferences and Seminars for Communicators
Publications Management Clinic, TECH*COMM 2001 Conference, and more http://www.SolutionsEvents.com or 800-448-4230
You are currently subscribed to techwr-l as: archive -at- raycomm -dot- com
To unsubscribe send a blank email to leave-techwr-l-obscured -at- lists -dot- raycomm -dot- com
Send administrative questions to ejray -at- raycomm -dot- com -dot- Visit http://www.raycomm.com/techwhirl/ for more resources and info.