While I appreciate the effort put into development, I have some questions about the underlying premise.
1. How do detailed metrics about coding sessions, git interactions, and test runs actually leads to meaningful improvements in your productivity?
2. Assuming you have used this plugin for a while now, how does tracking these metrics correlate with better code quality?
I hope I'm not coming across as overly critical, as that's not my intent. I appreciate the effort put into the development of software regardless of the final intent.
When I look at my own experiences, I wouldn’t focus strictly on code quality and productivity in the narrow sense. What I mean by that is that my focus on smaller commits and smaller branches helped team members understand changes more quickly, making knowledge transfer easier. For branches where code reviews/approvals were necessary, this helped our overall flow because stories were not blocked that long due to long-lasting approvals.
Another point was that, with Kasama, I was able to track the runtime of long-running tests and build tasks, which allowed me to point at tasks where optimizations were needed. Otherwise, such discussions were always based on gut feelings, and improvements were usually postponed…
While I appreciate the effort put into development, I have some questions about the underlying premise.
1. How do detailed metrics about coding sessions, git interactions, and test runs actually leads to meaningful improvements in your productivity?
2. Assuming you have used this plugin for a while now, how does tracking these metrics correlate with better code quality?
I hope I'm not coming across as overly critical, as that's not my intent. I appreciate the effort put into the development of software regardless of the final intent.