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: Thinking Patterns (was RE: Interviews (5 Year Question))
From: Jim Shaeffer <jims -at- spsi -dot- com>
Date: Mon, 18 Jun 2001 08:25:21 -0400
X-Message-Number: 5
> Referring to the original examples, a sequential procedure is also
> easier to program in a computer language than any process that
> involves if statements. In fact, the examples given are simply
> examples of technical writing that is programming certain behaviors
> into human beings rather than programming the behavior into
computers.
> While neither example is terribly complex, having more decision
> points causes more complexity and more likely points of failure.
Well, on example 2 I did cut the complexity short. I wanted a
comparatively quick example that illustrated the fun of documenting
something with decision points.
While I could have got a bit more complex, I didn't feel it was
necessary.
Believe me, our documentation coordinator doesn't exactly look forward
to me tossing the next chapter in the "Great Canadian Novel" in her
direction. She'd be a bit happier with a series of two page
procedures.
> Better programmers can handle more complex situations. Better tech
> writers can handle more complex situations.
Good point.
> However, I think it may be easier for us as tech writers to avoid
> complex situations for long stretches of time.
> Then, when we do need to address them, our tools are rusty.
Also good.
Whether we avoid them intentionally or not is, I suppose, dependent to
some extent on the environment we find ourselves in.
If the products and processes we are documenting lend themselves to
short sequential instructions, then those long stretches are forced
upon us. If we are in situations where the complex is the norm, then
we develop the skills faster.
--
John Fleming
Technical Writer
Edmonton, Alberta
email: johnf -at- ecn -dot- ab -dot- ca
*** Deva(tm) Tools for Dreamweaver and Deva(tm) Search ***
Build Contents, Indexes, and Search for Web Sites and Help Systems
Available now at http://www.devahelp.com or info -at- devahelp -dot- com
Sponsored by Cub Lea, specialist in low-cost outsourced development
and documentation. Overload and time-sensitive jobs at exceptional
rates. Unique free gifts for all visitors to http://www.cublea.com
---
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.
