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: No Time to Read From:"Cardimon, Craig" <ccardimon -at- M-S-G -dot- com> To:"Richard Lewis" <tech44writer -at- yahoo -dot- com>, "Nancy Allison" <maker -at- verizon -dot- net> Date:Fri, 10 Aug 2007 12:38:37 -0400
I agree with you in principle. It's your abbreviation of technical
writing to "TWing" that I can't quite tolerate.
I'm saying to myself, "What in the world is a T-Wing?"
It's all in how we think and interpret things. Maybe I'm weird. Shrug.
Craig Cardimon
Technical Writer
Marketing Systems Group
www.m-s-g.com
ccardimon -at- m-s-g -dot- com
267-558-3155
_____
From: Richard Lewis [mailto:tech44writer -at- yahoo -dot- com]
Sent: Friday, August 10, 2007 12:28 PM
To: Cardimon, Craig; Nancy Allison
Cc: Techwr-l
Subject: RE: No Time to Read
If one is going to go anywhere in life, he/she needs to be a big picture
person. Unfortunately, you can not be focused on the big picture and
the implementation details at the same time. One of the biggest
detractors to success in life is constantly having to focus on the
details. Such is a huge initiative killer in seeking the bigger
picture.
I tell my bank, no I am not going to study your 35 block quick-and-easy
flow diagram on how to reach customer service. I just want to pick up
the phone, call a number, and ask my question. That is all I am willing
to do; my time is for bigger issues.
In TWing, my focus on the big picture has enabled me to come into deeply
trouble large-scale projects, thrown away requirements specifications
that consisted of tons-and-tons of tiny little text, and then created
data flow diagrams with a little supporting text that saved the day.
<<
I've come late to this thread and am also going to wing it by
guessing
that the discussion is about naming a section that is for people
who are
unlikely to read the rest of the doc.
I humbly offer this revision of Craig's suggestion:
Instead of
>_For People Who Don't Have Time To Read Instructions_
I propose
"No Time to Read Instructions?"
Maybe someone else can whittle this down further, for those
really,
really busy people!
Create HTML or Microsoft Word content and convert to Help file
formats or
printed documentation. Features include support for Windows
Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular
help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as
tech44writer -at- yahoo -dot- com -dot-
Create HTML or Microsoft Word content and convert to Help file formats or
printed documentation. Features include support for Windows Vista & 2007
Microsoft Office, team authoring, plus more. http://www.DocToHelp.com/TechwrlList
True single source, conditional content, PDF export, modular help.
Help & Manual is the most powerful authoring tool for technical
documentation. Boost your productivity! http://www.helpandmanual.com
---
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-
