RE: Opaque objects and Emacs documentation

[Drew Adams]

> one writes documentation not merely
> for users, but for his fellow developers.
> (I guess this doesn’t apply to personal
> projects

It does.  Why?  Because we lose some degree
of familiarity with the code, and especially
with undocumented and unobvious "whys".

Communication not only from one human to
another, but from one human state, at one
time, to another state of the same human,
at another time, perhaps in another context.