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.
Just a couple of "aside" notes from a Power User, not a hacker:
1. I always read the "readme" because I once received a program that blew
itself up because I had not read the "readme" instruction regarding the
cockamaymee special procedure to be used for its installation. And they
resisted sending a replacement because I had obviously not read the
"readme". As hackers (programmers and technicians), they assumed that
everybody knew that it's important to read the "readme"; that's why it's
there and that's why it's called a "readme".
<if Trish Castin is on this list, please put down your coffee before reading
further>
2. According to most of the development people I've worked with, there is
no such thing as a bug. It's just an undocumented feature.
Dori Green
Technical Writer, QMS Project
Associated Brands, Inc.
WebWorks ePublisher Pro for Word features support for every major Help
format plus PDF, HTML and more. Flexible, precise, and efficient content
delivery. Try it today! http://www.webworks.com/techwr-l
Easily create HTML or Microsoft Word content and convert to any popular Help file format or printed documentation. Learn more at http://www.DocToHelp.com/TechwrlList
---
You are currently subscribed to TECHWR-L as archive -at- infoinfocus -dot- com -dot-