Kenny Billiau wrote:
* Continuously follow the progress of programmer's contributions * Discover the productivity drops early enough * Decide the value of programmer instantly, based on his contributions * Look at distribution of the project knowledge among your team * Inspect how the code of each programmer survives the test of time * Evaluate the code quality and longevity of each team member
*LoL*
I especially like the tag line of the website: WARNING: Up to 10% of your developers may be idle now!... yeah no shit sherlock, it's lunch .... :) Anyway, we don't need these stats to indicate how productive we are. We all now who the best programmers are: those with a pink keyboard ;) Back to work ... Michiel -- ================================================================== Michiel Van Bel PhD student Tel:+32 (0)9 331 36 95 fax:+32 (0)9 3313809 VIB Department of Plant Systems Biology, Ghent University Technologiepark 927, 9052 Gent, BELGIUM mibel@psb.ugent.be http://www.psb.ugent.be ================================================================== There is no peace among the stars, only an eternity of slaughter and the laughter of thirsting gods.