> User documentation, maybe. The real problem is a lack of code
> documentaton, and for that you need someone who understands code.
Code documentation (maintenance) only requires knowledge of the concept of
clean interfaces, and be able to recognise when a code checkin changes that,
and the ability to pester a programmer into explaining why the interface has
changed.
It would be wise to have a novice start on user documentation, however many
such novices would soon be able to communicate with programmers, and others
doing code documentation, at which point they are able to assist in code
documentation. This then provides a nice learning curve for people wanting
to actually get into programming.
> > Rather than have people request documentation updates, each checkin
could
> > pass by a documentation team who look for changes to interfaces, and ask
the
> > programmer questions until 'programmer speak' comes out as decent
> > documentation.
>
> I like that idea. It would probably be pretty slow however.
It would be slow until the documentation is up to date, however after that
point it could become a quality stage within the checkin process, making
programmers write a blurb any time they wish to break an interface.
John
