---------------------<snip>------------------
I would prefer to measure developers by inverting the cost of maintenance.
I don't want maintenance programmers to be productive, I want them to
be whithout anything to do ! ;)
Given that maintenance in many shops is defined in part as "minor"
changes to meet changing business and technical requirements, I don't
know that should be a complete goal. I realize the Object-oriented
and package crowds are closer to your view of things.
------------------<unsnip>-------------------
Personally, I like to see a relatively large and busy development staff,
with a much smaller maintenance staff that is also moderately busy.
Small changes, such as report headings, changes in tax rates, etc. can
be handled by the maintenance staff, as well as one-time requests for
special reports, etc.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
