An analysis is presented of the assumptions and research methods behind computer manuals for programmers and system administrators. The author builds an objective critique of current manuals' disjointed and legalistic approach. He also relates documentation issues to the structure of computer systems and to methods of development. Although analytical and theoretical, this critique offers concrete examples of better documentation and ends with a list of suggestions for writers.