4 ms·
I'm not sure I like this. It's generally considered that there's no effective way to measure productivity[0]. Whenever you introduce metrics, programmers end u
by cytzol 14y ago
I'm not sure I like this.
It's generally considered that there's no effective way to measure productivity[0]. Whenever you introduce metrics, programmers end up gaming it: pay them by lines of code, they write too many lines of code; pay them by commit, and they're going to start committing too much.
These graphs are going to just cause programmers to both commit in too small chunks (or splitting up a commit into several), or delaying some overnight so that they have a longer streak. I know that the data was there already, but now it's made visible, people are going to start commenting on how much I'm coding.
[0]: http://stackoverflow.com/questions/324399/what-is-a-fair-productivity-measurement-technique-for-programmers http://stackoverflow.com/questions/324399/what-is-a-fair-pro...
- tomchristie 14y agoI think it works really nicely. I wouldn't necessarily treat it as a measure of productivity, but it does help give an indication of consistency and trend. I also like the idea of annotating it (perhaps that'll come as a feature sometime) It'd be nice to be able to mark on coding sprints & events.