On Tue, 29 Jan 2002 "Ken Ray" <[EMAIL PROTECTED]> wrote:
(snip)
> That said, I don't think this is a matter of development vs. documentation;
> this only becomes a problem if the developers themselves are responsible for
> the documentation. I have worked with quite a few companies where there was
> one or more people who were assigned to documentation and support, and did
> not impede the progress of the development of the product. Perhaps all that
> is necessary is identifying someone who fits that bill (whether in-house or
> a consultant)?
This is a good idea for general documentation, but doesn't really
apply to the particular case of producing release notes that contain
lists of bugs reported and fixed or not fixed. That work can only
be done by a development engineer or at the very least a QA engineer,
which means you're either slowing development of the product itself, or
reducing the responsiveness and/or quality of the tech support the
company can provide (in addition to all the other disadvantages I
listed).
Regards,
Scott
> Just my $0.02,
>
> Ken Ray
> Sons of Thunder Software
> Email: [EMAIL PROTECTED]
> Web Site: http://www.sonsothunder.com/
********************************************************
Scott Raney [EMAIL PROTECTED] http://www.metacard.com
MetaCard: You know, there's an easier way to do that...
_______________________________________________
improve-revolution mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/improve-revolution
