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.
Subject:Now here's an idea... From:ejray -at- OKWAY -dot- OKSTATE -dot- EDU Date:Tue, 22 Feb 1994 08:07:19 CST
I just saw this on a different list (cello-l) that is
frequented by software developers:
>By the way, one clever fellow had a pretty good
>solution for [having a program which doesn't do what
>the users want]: write the user's manual, in as much
>detail as possible, before starting the design
>of the tool. You can't be influenced by the inner
>workings, which you don't know yet, and you can pass
>it around for criticism.
Now, doesn't this sound familiar? Takes our conclusions
a couple of jumps farther. Actually, it sounds like a
reasonably feasible idea, within reason. I haven't met
many programmers who would admit to not being able to