Interesting. Sounds like more Stream Analysis for Hongbing.
If Hackystat can analyze your development cycles (it sort of does
this already with the TDD analyses) we can open a new area of
Personal Development Process analyses. Something, which I still
think is lacking in Hackystat. I would like to learn more about how
I program and what my tendencies are when fixing a bug, adding a feature, etc.
Maybe I build too often, causing more dead time and cuts down my flow! Haha.
thanks, Aaron
At 11:07 AM 11/8/2006, Philip Johnson wrote:
Here's an interesting article about the "dead time ratio":
<http://www.oreillynet.com/onjava/blog/2006/03/dead_time_code_compile_wait_wa.html>
Kind of related to sixth sense software's 'flow time', but actually
measures something closer to the reverse!
Cheers,
Philip
