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.
Re: Resolved: Technical communicators can create information
Subject:Re: Resolved: Technical communicators can create information From:Keith Hood <klhra -at- yahoo -dot- com> To:John Posada <jposada99 -at- gmail -dot- com> Date:Sun, 13 Jun 2010 09:12:24 -0700 (PDT)
Does it matter? I don't think so. I figure that we simply find information and renoberate it a bit and pass it on. I don't care who or what "creates" information. That is not significant in my world. What matters to me is whether I can get a job manipulating information. And once I have a job, how well I do it.
If anyone wants to think they create information, fine. I guess it's a matter of how you define the word "create." If it makes someone feel better to think of themselves as creating, run with it.
What I really wonder about whenever a topic like this comes up is, why would people need to feel they are "creating" information? Why is it not enough to think of themselves as manipulating or refining information? It's long been my belief - founded on first hand observation - that when people start spending a lot of time and thought on the philosophical or metaphyhsical underpinnings of their work, it's because they're not getting enough out of *doing* their work. And that usually comes from not working enough.
I think that when people start to think of themselves as information "creators," it's because there is some part of them that has needs which are not being met by the work of being an information manipulators. In that case, maybe they should start thinking about a different line of work. Maybe they should look into a line of work where they are the ones who pass the information to the technical writers.
--- On Sun, 6/13/10, John Posada <jposada99 -at- gmail -dot- com> wrote:
From: John Posada <jposada99 -at- gmail -dot- com>
Subject: Re: Resolved: Technical communicators can create information
To: "Keith Hood" <klhra -at- yahoo -dot- com>
Cc: "TECHWR-L Digest" <TECHWR-L -at- lists -dot- techwr-l -dot- com>, "Steven Jong" <stevefjong -at- comcast -dot- net>
Date: Sunday, June 13, 2010, 11:33 AM
Then who or what does?
Also...maybe your definition is different than mine.
In your eyes, what is information?
On Sat, Jun 12, 2010 at 11:36 PM, Keith Hood <klhra -at- yahoo -dot- com> wrote:
Right. But explaining is not creating. We figure it out, we deduce it, we compare things until we go "Aha!" but we don't create it. I'm willing to call myself an information monger but I think calling myself an information creator is a bit too grandiose.
Senior Technical Writer
NYMetro STC President
Gain access to everything you need to create and publish documentation,
manuals, and other information through multiple channels. Choose
authoring (and import) as well as virtually any output you may need. http://www.doctohelp.com/
- Use this space to communicate with TECHWR-L readers -
- Contact admin -at- techwr-l -dot- com for more information -
You are currently subscribed to TECHWR-L as archive -at- web -dot- techwr-l -dot- com -dot-