3 ms·
Going through the same process myself, short answer there is no easy metric that you can add that really quantifies a developer. I would start measuring projec
by allanmacgregor 11y ago
Going through the same process myself, short answer there is no easy metric that you can add that really quantifies a developer.
I would start measuring projects or teams first, getting a solid set of metrics for each and once you have that you can start tracking down individual developers.
Even so tracking developer productivity can be hard, a good chunk of our work happens in our head. Who is more valuable the developer that wrote thousands of lines of code or the one that changed one but fixed a critical bug in production?
I highly recommended this book http://shop.oreilly.com/product/0636920020134.do http://shop.oreilly.com/product/0636920020134.do
- ctoestreich 11y agoMoreover, "bugs" can linger around in code for a long time and you can't really track that metric. Code changing over time in a repository could be to fix bugs or refactor/rewrite etc. I think the original posters question was more around whether there are existing resources to track these things to which the answer I feel is no. Combining blogs posts, stack exchange score, speaking topics and other real world things can give you some semblance of a developers engagement with the development community but doesn't translate one-to-one on their actual productivity levels on a team. Although these things usually indicate a greater potential for success.