Open any developer's GitHub profile and you'll see a grid of green squares—their "contribution graph." It's become an unofficial resume, a visual representation of coding activity. There's just one problem: it's largely meaningless.
The Commit Count Fallacy
Commits are a unit of version control, not productivity. A developer who makes 50 tiny "fix typo" commits isn't more productive than one who ships a major feature in 3 well-structured commits.
Consider what the contribution graph doesn't show:
- Time spent thinking, designing, and planning
- Code review and collaboration
- Debugging sessions that don't result in commits
- Documentation and knowledge sharing
- Work on private repositories
- The actual impact of the code committed
Gaming the System
Because contribution graphs are visible, they create perverse incentives. Some developers commit constantly to maintain "streaks." Others automate commits to keep their graphs green. The metric becomes the goal rather than a reflection of actual work.
A More Complete Picture
DevClocked tracks more than just commits. By monitoring editor activity, file changes, and session duration, we can show the complete picture of development work—including all the time spent that never results in a git commit.
The result is a more honest representation of developer effort, one that values thinking as much as typing and planning as much as pushing.