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:Our company's products From:Karen Kay <karenk -at- NETCOM -dot- COM> Date:Sun, 19 Nov 1995 19:33:08 -0800
At 01:17 PM 11/19/95 EST, Peter Kent wrote:
>Nobody told me I had to have a blind belief in all things technological just
>because I write about technology!
This reminds me of a question that I've been meaning to ask. I recently
accepted a staff position at a small-but-growing company. I'm impressed both
by the company's software and by the documentation for that software. I also
really like the tech pubs manager and the writers (mine is an editorial
position to start with), so it's altogether a very pleasant situation. Only
15 minutes from home, too, which is a minor miracle in the Bay Area.
So, I guess what I want to ask is, Is everyone proud of what their company
turns out? Do you feel like you're writing good documentation for bad
software? (I guess this goes back to the writing-around-design-flaws
thread.) Was your company's documentation good before you started working there?