Metrics built on the work itself
GitObs started from a simple idea: the most honest record of how a team builds software is the history it already keeps in Git. No timesheets, no surveys, no new tool for developers to feed.
Why Git
- Everyone already uses it. Every change to the code passes through it, so nothing has to be logged twice.
- It records collaboration. Who works on what, who reviews whom, and how knowledge moves through a codebase.
- It keeps the whole history. Trends over quarters and years are there from day one, not from the day a tool was installed.
How we think about measurement
Metrics should help a team see its own work more clearly, not rank the people doing it. Numbers that are used to judge individuals stop describing reality as soon as people learn to move them.
So GitObs describes repositories, teams and processes rather than scoring individuals.
What happens next
More and more code is now written with coding agents, and the same questions apply to them: what did the work cost, how was it done, and what shipped? The GitObs team now builds AgentsTrack to answer them. Read about the move.