A bug might be as simple as a single character fix on a printed string, or as complex as performance isn't as good as we expected, so profile and rewrite parts of the entire application to get acceptable performance. Both count as a single unit in your "bugs fixed" metric.
Or do we have meetings to play poker and assign points for bugs?
Unless you're fixing tens of thousands of bugs I don't think you're going to have a good sample size to judge the output of 2 people based on just how many bugs they've closed.
This can also be gamed ie. pick up easier bugs to appear more productive, open bugs for small issues you notice yourself and fix, and this has the byproduct that real work never gets done.
Rewrites, infrastructure, code reviewers, mentoring. No earned dollars, no "features" shipped, good luck measuring "saved engineering hours".
There are no objective measures of productivity in the majority of cases for tech workers.
Infrastructure is a feature in and of itself. Besides, doing things like improving a build system to reduce build times, or streamlining code review workflow has clear measurable impact.
Every rewrite must have an observable measurable impact, otherwise it is simply not worth doing.
Your mentees' performance is an excellent proxy to measure your quality as a mentor.
Again, all of these can be assessed without much hand-waving.
Code reviews shouldn't even count towards your performance. It's just something that you have to do. (though arguably, if you have to do a lot of code reviews, then it's a clear signal that you're a valuable person on the team who knows a lot of detail about the system).
> There are no objective measures of productivity in the majority of cases for tech workers.
I think there clearly are, and I just listed some of them. Sometimes they're hard to boil down to a single number, but in most cases you can easily tell who's doing meaningful work.
Unless you're fixing tens of thousands of bugs I don't think you're going to have a good sample size to judge the output of 2 people based on just how many bugs they've closed.
This can also be gamed ie. pick up easier bugs to appear more productive, open bugs for small issues you notice yourself and fix, and this has the byproduct that real work never gets done.
Rewrites, infrastructure, code reviewers, mentoring. No earned dollars, no "features" shipped, good luck measuring "saved engineering hours".
There are no objective measures of productivity in the majority of cases for tech workers.