Earlier quoted context omitted.
I'm usually one of the strongest developers on my team, even when I'm managing. It's one of my strengths and why I stay with small companies. It also means I'm qualified to judge the technical skills of my developers, I know how long it should take. People who think judging performance is hard have a broken development methodology or no technical chops. That's also why I included the comment on my own rankings; I hav…
>People who think judging performance is hard have a broken development methodology or no technical chops. And this is exactly why I asked the question. Here you have judged me, since I said judging performance was hard, on both my development methodology and technical chops. Yet you know nothing about me at all. The problem of evaluation is an important one, and one I'm always interested in reading more on. Unfortun…
I've never had a problem judging performance when I was doing my job right. Any time I've been unsure it's because I was either not managing the team properly or did not have enough technical knowledge to evaluate the estimates and claims (e.g. this took longer because of X and Y).
I know you can manage performance in a way that allows evaluation even if you don't have the technical chops to evaluate it technically, because I have seen technically weak peers do a good job of it.
I didn't discard the reports of my peers. I noticed a trend of the peers who liked me rating me higher in areas of weakness (as perceived by both myself and my boss) than my skills deserved.
Data that contains some bias is not useless if you can adjust for the bias.