seven rules for sound documentation:
- write from the reader's point of view
- minimize repetition
- "avoid ambiguity"
- "use a standard organization"
- "record rationale"
- "keep documentation current but not too current" (meaning, don't change the documentation immediately when a change is made; it should have defined release cycles, times when all of the pending changes are made at once)
- "review documentation for fitness of purpose"