Re: Purpose Driven Technical Writing

[Al Geist <al -dot- geist -at- geistassociates -dot- com>]

Okay...pet peeve time.  According to Theodore A. Cheney in "Getting the 
Words Right,"

"Utilize is not an elegant variation of the word use; it has its own 
distinct meaning.  When you utilize something, you make do with 
something not normally used for that purpose, e.g., you 'utilize' a dime 
when a bloody screwdriver is nowhere to be found.  If the screwdriver 
where there, you'd 'use' it, not utilize the stupid dime for the 
purpose.  The computer went off-line, so tehy utilized Mr. Wangs abacus, 
the one he liked to use.  Despite the temporary breakdown, the 
computer's use-rate was up (not its utilization rate)."

So, you would have "extensive experience using rigorous end-user task 
analysis techniques...."

This is not to say that I agree with any of Tony's DFD arguments.  I 
agree with Oja that they appear to be nothing more than a new name for a 
flow chart, something that has been used since code was printed on 
Hollerith cards.

sburnf -at- au1 -dot- ibm -dot- com wrote: