On Tue, Feb 2, 2010 at 09:18, Viktor Klang <[email protected]> wrote: > On the topic of LoC, please read Uncle Bob's latest: http://bit.ly/cYQlvB
Liked that article. Regarding LOC or number of classes or whatever statistic that covers code or tracks issue solving: a) Coding is only a part of the development process - I know it very well from being urged to be more productive - planning time is short and so often a suboptimal solution is implemented because the software is not well designed. b) Depending on particular tasks the relation between e.g. documentation to be read and coding itself can vary dramatically. (I am currently working on a project where I have to read and understand about 300 pages of standard specification - so days of reading before writing any line of code or producing any class.) c) Whatever measurement you use, people will focus on optimizing the main parameters, e.g. write as many lines as they can (even if not necessary) produce a class for every sh*t or even - I experienced that also - prefer topics being closed ASAP after opening. I noticed that on several projects that if there is a duplicate of a bug, they close the original one and leave the duplicate open. - Very good if open-status-duration is taken measured productivity - every duplicate is welcome. So productivity should be measured by gut feeling of the overall results and feedback from users and customers - and if you measure time required to implement new stuff or fixes then you need to measure that long-term! - Mr. Uncle Bob points that out very well. -- Best regards, Martin Wildam -- 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.
