This is Austin Salonen's Typepad Profile.
Join Typepad and start following Austin Salonen's activity
Join Now!
Already a member? Sign In
Austin Salonen
Recent Activity
(I think this idea is an extension of Pete's) The best extraction of this data, in my opinion, would be per source code file grouped by a time frame (say a month). Ideally the first value would be high as you're checking in several features but then it would trend to zero very quickly. Then you should be able to attribute later blips to bug fixes. If instead you have any other trend the code most likely really bad -- lots of bugs over time or new features require more commits (the code is likely violated the OCP) -- and should be refactored.
Toggle Commented Jan 27, 2011 on Measuring the Closure of Code at Michael Feathers
Austin Salonen is now following The Typepad Team
Jan 27, 2011