> More documentation was gradually written by technical writers, less by programmers. That led to some better explanations, some longer explanations, to lots of words, and here and there to meaningless drivel. ... "SetFoo sets the foo" without mentioning either the nature or details of foo. Written by someone who didn't understand what foo is or what matters about foo.
This is a process problem more than anything. If the technical writers don't understand the problem or solution then people either aren't communicating, the writers don't have sufficient access, or the writers aren't qualified.
This is a process problem more than anything. If the technical writers don't understand the problem or solution then people either aren't communicating, the writers don't have sufficient access, or the writers aren't qualified.