|
|
|
|
|
by foopod
1695 days ago
|
|
Most methods are poor. PRs and commits can easily be gamed and generally the best developers are the ones with succinct small changes that deliver high value. Two ways I have found to measure a developer's productivity are... 1. Based on the feedback of their peers. It helps to know the team members and the team's dynamics though. 2. Based on the $$$ the team bring in. Depending on how the team operate this could be far from their control though, a lot of decisions about the product will be out of the developer's hands. |
|