WakaTime – Quantify your coding
wakatime.com
wakatime.com
Also: http://martinfowler.com/bliki/CannotMeasureProductivity.html
As a proper Emacs user I also do my e-mailing there and my e-mail is in a git repository. Whenever I feel like I haven't got much done in a day I can usually verify that I it was because I spend like half a day writing e-mails instead of coding.
One of the more surprising stats I have found out about myself is that I regulary spend about 5% project time writing git commit messages.
I actually find the most value of wakatime that I can keep track of that I don't work too much on the "wrong" projects. Wakatime has helped me hold off things I should not focus on that much.
Wakatime has at least somewhat reduced my imposter syndrome tendencies because I can use it to disprove the feeling that I'm not getting things done because it tells me that I got things done even if it was not the things I originally had plan to get done.
I went to the site hoping that it would explain what metrics it is gathering and why those metrics might be useful. It might just be me, but I couldn't find that information.
You can also compare yourself to other developers, aka a leaderboard.
That's a feature with negative value. Top developers, at least in a business context, are those that help business realize their goals for their web product. One way top developers do this is to find solutions that involve writing less code, since code is a liability.
http://www.citeulike.org/group/3370/tag/hackystat
The first one, "Searching under the streetlight for useful software metrics" is our attempt to summarize the strengths and weaknesses of this approach.
There are significant challenges associated with making this kind of data actionable, and significant political/social issues associated with collecting this data at all.
What are they doing with my data?