[hirako2000]

These "quantified self" stats provide countless insights.

One example.

There is a refactoring view in there. By time, by projects, even breaking the figures down by type of actions.

Benefits:

- Self awareness. It is hard to gauge how much time is spent refactoring. If your priority isn't to refactor but meet a soon coming deadline, these stats tell you whether you are adhering to the priorities.

- Quantifies. If you are trying to explain to your colleagues that you find yourself needing to do a lot of refactor for that particular project, you've got numbers to communicate. What's a lot? Some colleagues often ask.

- Evidence. Showing these numbers communicates better certainty than "I think I've been doing a lot of refactor on this project today"

Plus, oftentimes with visualisations, we don't know what we are looking for. Until we find it.

[The_Colonel]

I use refactoring tools all the time during development and bugfixing. The distinction between refactoring / feature development / bugfixing is mostly in the intention. If it just tracks the usage of refactoring tools, I think there will be many false positives.