First Look:Development Stats using StatSvn
I am a big fan of The Daily Grind at
Larkware, as they often give out great links for new tools for developers. Today I was curious about a
Subversion metric report called
StatSvn, and decided to try it out. I have recently turned to
SubVersion for source control, previously it was zip, label the zipfile according to date/time modified, unzip for modification and the whole cycle starts allover again. Currently I'm the only one doing the version control, the others are still doing the same thing, however I will be giving them a presentation/demo about this cool source control as soon I get to configure our source server.
After downloading and following the usage in it's
online manual, I decided to check how I was doing with my development on our in-house applications. I tried on a module that has often so many change-requests:Patient Billing.
I was both amazed and worried about the results:
From the Report:
1.) I'm more productive, or at least commits often, during Sunday and during 10am, which is understandable because they're the busiest time.
2.) I'm not doing anything during Monday? Probably because I finished almost everything during Sunday hehehe
3.) I've only commited 500 times? I guess not bad since became active with Subversion late Sept-early October this year.
4.) Wow, we're already doing 150K LOC for one module alone.
4.) I've also subVersioned temporary directories, it was sitting there for months. Time to delete that.
5.) Able to refactor down the code to several thousands( 10K) off the 150K loc; I haven't verified if I have refactored it this much, but if I did that should be a pat to myself already.
This is just the tip of the Iceberg, I'll get to learn more about how to better myself developing as statSvn will show me as I progress.