Hacker News new | past | comments | ask | show | jobs | submit login

Exactly. Years ago, one company I was at proposed we start a bonus plan based on lines of code. I wrote a script that inspected the RCS commits (it was years ago) and generated a report that showed that most of our best developers were net negative lines of code.




And how did you define and measure the "best developers"?


1.) When I am stuck on hard problem, he is a good bet for help.

2.) History: was assigned tasks or project multiple people failed previously and was first to succeed.

3.) Tasks and projects assigned to him/her move with reasonable speed, does not need handholding. When other people take over, they don't complain all that much and are able to continue without encountering major wtgs.


People getting important shit done.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: