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.
> 2. (Likely) ... If you understand the
> programming language, you might also be able to extract
> some meaning from the _comments_ added to the source code,
> particularly if the development manager enforces good
> commenting practices (i.e., embedding explanations for
> program logic, variables, etc. directly in the source code).
Geoff's advice is good, but beware: the comments don't always get updated
when the code is updated. If you're working on a version 1.0 the comments
should be reliable. The higher the version number, the more out-of-date
the comments will be.
Regards
---
Stuart Burnfield (slb -at- fs -dot- com -dot- au) Voice: +61 9 328 8288
Functional Software Fax: +61 9 328 8616
PO Box 192
Leederville, Western Australia, 6903
