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.
Rather than have your programmer read a book, I would suggest you get the programmer to try writing some procedures, specs or whatever, and bring them to you for discussion and comment. Start your own little mentoring program, as it were. It's a much better way for a programmer to learn to write.
Then, after you have some experience with this individual and perhaps the mistakes that he or she tends to make (too much passive voice, doesn't use commas well, doesn't know ensure from assure, etc., etc.), then maybe you can do a little focused lecturing backed up with copies of the pages from the good books that cover the problems.
Bill S.
>>> Danny Ramsey <danny -at- REBOL -dot- COM> 07/06/99 05:31pm >>>
Please recommend to a programmer a useful book on technical writing of
software user manuals. Thank you.
