Now with the major objection to objective performance review gone we can do that for the actual individual contributors.
If the people near the top of those leader boards are near the top of the comp leaderboard your job is done as that makes sense by the numbers, if not you need a really good justification as to why* if you want to keep those literal top performers for long.
*or crossed fingers nobody discusses comp before you exit
> Lines of code (not just in main but in branches)
IMO, the best devs can end up with negative LOCs per measurement period. Neophytes will never have negative LOCs. Mediocre devs who copy and paste a lot can have really high LOCs.
> lines of documentation written
And the more documentation you have the more out of sync it is with reality.
I haven't really encountered this. Generally speaking people who can teach others to be much more productive like that are unsurprisingly themselves, more productive.
This fictional person would be better suited to a people management or coaching role as a individual contractor they only achieve a third of the average.