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.
Re: How much documentation for 1000 hours of programming?
Subject:Re: How much documentation for 1000 hours of programming? From:Charles Cantrell <chc -at- ONTARIO -dot- COM> Date:Fri, 29 Mar 1996 14:09:47 GMT
While I agree with everything you have said in
particular, I think when you get a large enough sample
set (enough documentation projects), that on average
about 10 hours of documentation per 100 hours of
programming can generally get the job done.
