|
> Maybe it's just a matter of expectations, but we expect 4 programs per > day, per programmer, since they just have to test compatibility of > standardized modules, not redesign nor rewrite as you state. Again, we are > testing dates, just dates. I don't see where that requires > redesign/rewrite of ANY application. 4 a day? If your code is clean enough that a programmer can do 4 a day then your code is probably already fixed. Otherwise I'd bet you will find there are sources missing, or misplaced, level-check problems, files with bad dates, conversion problems that are not as simple as expected, and old programs that no one has looked at in 5 years and don't make sense. Add in to that time for training sessions, vacations, days that don't go right, and employee turn-over and you'll be lucky to average 2 a day, imho. ---------------------------------------------------- Booth Martin --------------------------------------------------- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to "MIDRANGE-L@midrange.com". | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.