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:SUMMARY: Specialize or Die From:"Edwin Wurster" <eawurster -at- hotmail -dot- com> To:"TECHWR-L" <techwr-l -at- lists -dot- raycomm -dot- com> Date:Tue, 18 Dec 2001 15:34:17 -0500
Thank you for your participation.
Ed asked how tech writers would answer the following question in an
interview:
Q: Do you have a specialty within tech writing that you prefer?
Ted Rainey:
I have to say, overall, I enjoy working with Unix and creating documentation
for the Unix versions of the software much more than working with the
Windows side.
Steven Brown:
I've also had a life-long interest in construction
equipment, so my dream job is to work for Caterpillar,
writing product manuals and training material for
bulldozers, excavators, etc.
Karen Bush:
My response to the question re specialty preference within tech writing
would be instructional design, content manager.
Bruce Byfield:
Yes. Being a generalist.
Being a specialist might land you one particular job, but if the job
disappears or the specialty falls out of demand, you could be out of
luck. The best you could do is find another specialty as quickly as
possible. By contrast, a generalist can cope much better with a changing
situation.
Margaret Cekis:
Given a choice of opportunities, I tend to pick the one with the most
interesting technology or something novel about it. I couldn't face a
permanent position where every year I was required to update the same set of
inventory program manuals.
Martha Jane:
My answer is a definite Yes. I much prefer documenting complex
software-development tools and methodologies for developers.
Earl Cooley:
I prefer to specialize in technical writing that involves the
use of the English language.
Linnea Dodson:
I tell people I'm a "professional end user." I'm happiest when doing user
guides and doing things to software that engineers think nobody would ever
do to it.
Elna Tymes:
My firm specializes in several things:
1. Getting projects done on time and on budget.
2. Keeping our agreements. Period.
3. Coming up to speed quickly and being flexible.
4. Staying abreast of latest technology, especially in telecommunications,
security, databases, and presentation of information.
Andrew Plato:
???
Ed Wurster:
I prefer working on end user documentation as part of the development team.
Although this costs a business more than coming in late and "mopping up," it
tells me that a manager is aware of how poor or inadequate documentation
affects future support costs.
Edwin A. Wurster
______________________________________________
17 Hollybrook Way | Voorhees, NJ 08043
856-435-7823
______________________________________________
Consulting, Programming and Maintenance
for PC & Mac Systems/Network
______________________________________________
Training, Technical Writing and Web Design for Small Business
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Collect Royalties, Not Rejection Letters! Tell us your rejection story when you
submit your manuscript to iUniverse Nov. 6 -Dec. 15 and get five free copies of
your book. What are you waiting for? http://www.iuniverse.com/media/techwr
---
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.