technical writers are masochists

[Eric Richardson]

Trent Shipley wrote:
> 
> <vent_mode>
> 
> Is it standard practice for the programming/engineering staff to say we have
> done a s??t-load of modifications to the software.  It is now on the server.
> Please log on and figure out what the modifications are.  We are much too
> important and busy to give you a list of the modifications.  When you have a
> list of modifications, please figure out what they probably do, then submit
> updated drafts of the documentation that we never reviewed the last time you
> submitted them for review.
> 
> What if the programmer is also the owner of the company?
> 
> They actually resent my asking for developer specifications, expecting me to
> configure the application, run test cases, and deduce from the application's
> behavior what functions, features, database fields, etc. actually do.
> Asking questions about the application is regarded as wasting their time
> with *estupiiid* questions.
> 
> </vent_mode>
> 
> Any advice on how to manage the manager?
> 
>    Any advice on how to *become* a programmer or manager?

I noticed in the Xalan project, xml.apache.org, that they extract CVS
info on changes automatically into the documentation. In the Extreme
Programming process, the developers should probably make sure the
documentation, test cases and everything is in sync all the time. Look
at Extreme Programming Explained by Kent Beck ISBN 0-201-61641-6. There
are also more books on XP as well.

Eric