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.
Carolyn wrote:
>He stated on frequent occasions that spelling was superfluous and unimportant.
One time a committee reported to the Information Development department
proposals for measuring quality. One of them was "correct spelling". An old
tech writer and editor, who had literally written the book on parts of the
subject, spoke up from the back of the room: "Correct spelling is not a
quality indicator; it is a condition of employment."
>We are required to *document the software application* rather than
>write a manual that will actually help our users do their jobs better
>and more easily
These are two different but equally worthy efforts. If you want to do the
latter, you have to develop a business case showing that it is needed and that
the present documentation isn't adequate. It also would help if you could show
that more writers won't be needed because the present documentation isn't
really needed.
