Teamwork in version two was just as good as it was in v1.0's development phase. We met regularly on IRC, and with the assistance of a python bot I wrote, we get commit logs posted directly into the channel. We discuss design and divide the work there and on the phone.
What was really interesting was the opportunity to employ a new tool called Hackystat to measure the health of our project.
Here is a screenshot:
Hackystat is a great way to monitor your project as it computes various statistics about how your project is performing.
"Hackystat is an open source framework for collection, analysis, visualization, interpretation, annotation, and dissemination of software development process and product data."Hackystat works by relying on the user to install sensors in their project as well as their IDE. It dispatches data to the Hackystat server every 5 minutes (in IDE) and everytime ant is invoked. The kind of information that is transmitted is related to the files your working on and the time you spend on them.
This application can answer questions like these:
- What day and time during the month was Oahu energy usage at its highest? How many MW was this?
- What day and time during the month was Oahu energy usage at its lowest? How many MW was this?
- What day during the month did Oahu consume the most energy? How many MWh was this?
- What day during the month did Oahu consume the least energy? How many MWh was this?
- What day during the month did Oahu emit the most carbon (i.e. the "dirtiest" day)? How many lbs of carbon were emitted?
- What day during the month did Oahu emit the least carbon (i.e. the "cleanest" day)? How many lbs of carbon were emitted?
You can download our distribution here: WattDepot CLI v2.0
What code coverage percent are you aiming for? I think there are diminishing returns as you get closer to 100%.
ReplyDelete