ASIDE:
Your manager is an idiot.
The most productive programmer may well be the one removing the most code
each day/week/month
The number of bugs is a function of the number of lines of code, therefore
the more lines of code you write the more bugs you write and the harder it
is.
This is a dangerous road for the manager to go down...
Once he/she starts down this road you will have developers committing
changes
with
lots
of
padding
whitespace
"to
make
the
code
easier
to
read"
So the next request you will have to respond to from your manager is to
count the "non-blank" lines of code...
/*
*
* Comments are great for making code more readable.
*
*
* No body has ever been shot for putting comments into code to help the
people maintain the code
*
*
* Though if you have seen some of the comments I have, perhaps some should
have been
*
*/
So expect about 1 performance review cycle later to be asked to filter out
comments....
private static void rainyDayMethod() {
int foo=0;
foo++;
foo++;
foo++;
foo++;
foo++;
foo++;
foo++;
foo++;
foo++;
foo++;
foo++;
foo++;
foo++;
foo++;
foo++;
foo++;
foo++;
foo++;
foo++;
foo++;
foo++;
}
Add that to any class you feel like and... presto chango... your manager
now will be asking for you to filter out "dead code" and "unused
methods/classes"
This metric is far far far too easy to game.
Ask your manager to reconsider.
On 29 August 2012 09:48, fried noodle <hutieu...@gmail.com> wrote:
> Hi,
>
> Are there any plugins for Jenkins to show a report about the lines of code
> commited by each developer in a particular period (days, weeks, months)? My
> manager wants that data to keep track of team's productivity.
>
> Many thanks in advance.
>
> Tai
>
