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.
> Does that mean that I am not a technical writer because I don't have a
> degree, or does that make me a professional tech writer because I take
> more pride in my work than a diploma?
Careful, careful! Here there be flamewars on that topic! <g>
The point you made
> how many companies
> are going to be willing to PAY for a person who understands ALL facets
> of the technology they are writing about, AND can communicate the
> information they know to others with absolutely NONE of the same
> knowledge?
is why there are people making big money doing information systems
consulting these days. While it's difficult getting into the business,
especially since you're competing with the likes of Andersen
Consulting, Price Waterhouse, etc., it's my personal opinion that this
is A direction technical communication is heading.
My company now takes the view that we design what we call "meta
information" systems, where training, documentation, and online Help are
AMONG the forms that information gets delivered to the right customer.
There are other forms, too. Further, because correct input can affect
how the information gets passed along, we target that too.
