I've used this: http://cloc.sourceforge.net/
It's quite neat, however, I couldn't reconcile its answers to reality :) Based on the loc it reports, all the teams I have worked in have been WAY off the charts in terms of productivity compared to the numbers found in Code Complete etc for programmer productivity. So, you need a block (not a grain) of salt. There is no one measure you can use... and if your are a manager nothing beats getting in and looking at the developers commits.... On Feb 2, 7:11 am, jr <[email protected]> wrote: > Hello Everyone, > > I have a question that might be a bit polemic. I would like to know > what approach do you take to measure productivity on a Java project. > If we speak just about lines of code, how do you measure them, how do > you filter non-redundant files from the redundant ones. > > Thanks > JR -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
