Reputation
201
Top tag
Next privilege 250 Rep.
View close votes
Badges
1 4
Newest
 Yearling
Impact
~5k people reached

  • 0 posts edited
  • 0 helpful flags
  • 17 votes cast
Feb
9
comment Annual Review: what hard data should a developer bring?
All those number you come up with are highly subjective and therefore imho of not much value at all. I understand that these number can portray value, but imho they can just as easily get you into trouble for twisting the truth. E.g. you close 40% of the bugs .. those are all going to be of different complexity and workload. You will also have taken a different amount of help from others for them and so on. Or you could have just done the closing of the bugs and not actually the development. So really the 40% number does not mean much at all. And that applies to pretty much all metrics..
Feb
9
comment Annual Review: what hard data should a developer bring?
So how are you going to come up with these numbers so that they are even remotely true and reflect your input in a team environment? I doubt thats possible...