Author here, I wanted to track how much time I spend on certain feature branches. Existing solutions either asked me to create yet another online account or required me activate/deactivate timers manually. When your internet is connection is flaky or you forget a timer once any estimations instantly become useless. I wanted something that was automatic and 100% offline, so this weekend I created “Timeglass”. It uses file monitoring and git hooks to make sure you’ll never forget to start or stop your timer ever again. Let me know what you think!
Though this will catch the obvious cases where you should be billing but aren't while actively writing code, what about doing research or reading? Or code reviews? In a sufficiently complicated codebase, it might be the case that you're reading and thinking a lot longer than you're actively writing…<p>It is pretty neat to see the time spent actively writing each commit, though, and the file monitoring provides a better check than just looking at the delta between timestamps, so bravo for that!