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.
Dave Wood wrote:
<snip>
This begs a question I have frequently asked - Why is it that
Microsoft gives us inadequate manuals (if any) with their
products, but there are plenty of "Getting the Most Out of ..."
titles available from (you guessed it) Microsoft Press.
Simple. The user guides, technical references, and so on are on a different
schedule, with different priorites. The User Education books have to meet
the ship date, have to document every feature (no matter how obscure,
complicated, or powerful), and have to aim at all users (lowest common
denominator).
The MS Press books focus on just the really exciting, cool, beneficial
features while glossing over the pits and wrinkles. Press and third party
books don't have to meet the scheduled release date, don't have to bow (as
much) to internal politics at MS, don't have to fit the same rigid corporate
style, tone, and organizational guidelines, and don't have to document
everything while everything is changing.
Anyone can prepare a book proposal and submit it to MS Press (or at least, a
few years ago anyone could). Some TECHWR-Lers have written aftermarket books
(not me).
Aftermarket writers have a little more freedom to say "this might be a
strange method, but you really can do such and such." A staff writer has to
pretend that all functions and features are equally beautiful and useful.
Staff writers have to make global decisions and stick with them: teach mouse
or keyboard always, teach the menu way or the shortcut way always. An
aftermarket writer has a little more freedom to present the tasks as best
fits an individual task, without being seen as ruining the corporate image.
Beryl Doane, a recovering microsoftie
bdoane -at- intermec -dot- com
TECHWR-L List Information
To send a message about technical communication to 2500+ list readers,
E-mail to TECHWR-L -at- LISTSERV -dot- OKSTATE -dot- EDU -dot- Send administrative commands
ALL other questions or problems concerning the list
should go to the listowner, Eric Ray, at ejray -at- ionet -dot- net -dot-
