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.
Several of you were very helpful in suggesting what questions needed to
be addressed for our potential hire of someone to do what was referred
to as code documentation. I queried management on exactly what they
wanted documented and warned them of the intractability of getting code
documentation from 300,000 lines of uncommented code. Got no responses
except a need for documenting build procedures.
Result: we hired a tech writer who has strong UNIX skills, so he can
jump into documenting build procedures and installation guides. He'll
spend the rest of his time documenting new products for users, and
report to me.
