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.
Has anyone ever met a programmer who liked to write error messages?
Everywhere I worked, it was on the agenda to pass this task over to the
tech. writers, but this never happened, for a variety of reasons.
1. Time--write those error messages fast, cause you don't have time to
explain it to a writer and the product goes out TODAY.
2. Writer brought into process too late, as an after-the-fact and not
terribly necessary part of the process.
3. Software not available for testing by writer (who can then edit the terse
programese that the developer is obliged to provide) until too late.
Or, to mimic the phrase about how to make a business a success:
"There are three impediments to writers writing or editing error
messages: time, time, and time."
Gwen "sorry_about_the_formal_signature_forgot_to_change_it" Gall