Comments on: 5 code metrics you need to watch http://maxheapsize.com/2010/02/23/5-code-metrics-you-need-to-watch/ Oliver Wehrens on Programming and Agile Sun, 24 Jul 2011 10:50:52 +0000 hourly 1 http://wordpress.org/?v=3.1.2 By: Source Code Metrics Tool http://maxheapsize.com/2010/02/23/5-code-metrics-you-need-to-watch/comment-page-1/#comment-17904 Source Code Metrics Tool Sun, 24 Jul 2011 10:50:52 +0000 http://maxheapsize.com/?p=459#comment-17904 Source code metrics like WMFP can give you a good indication of how maintainable your code is, quantity wise, since it can estimate the development hours it took to code the source file (which is directly related to how much effort is required to maintain the code) Source code metrics like WMFP can give you a good indication of how maintainable your code is, quantity wise, since it can estimate the development hours it took to code the source file (which is directly related to how much effort is required to maintain the code)

]]> By: SM http://maxheapsize.com/2010/02/23/5-code-metrics-you-need-to-watch/comment-page-1/#comment-4889 SM Fri, 26 Feb 2010 11:51:37 +0000 http://maxheapsize.com/?p=459#comment-4889 Helpful post. Thanks Helpful post. Thanks

]]> By: Oliver Wehrens http://maxheapsize.com/2010/02/23/5-code-metrics-you-need-to-watch/comment-page-1/#comment-4847 Oliver Wehrens Thu, 25 Feb 2010 14:28:03 +0000 http://maxheapsize.com/?p=459#comment-4847 @Kostis: I will check it out, thanks @Kostis: I will check it out, thanks

]]> By: Kostis http://maxheapsize.com/2010/02/23/5-code-metrics-you-need-to-watch/comment-page-1/#comment-4845 Kostis Thu, 25 Feb 2010 12:52:28 +0000 http://maxheapsize.com/?p=459#comment-4845 Another good metric is the "Distance" as reported from JDepend. Sonar also includes it and suggests that values less than 20% are optimal. Another good metric is the “Distance” as reported from JDepend. Sonar also includes it and suggests that values less than 20% are optimal.

]]> By: nitramf http://maxheapsize.com/2010/02/23/5-code-metrics-you-need-to-watch/comment-page-1/#comment-4841 nitramf Thu, 25 Feb 2010 10:17:07 +0000 http://maxheapsize.com/?p=459#comment-4841 <p>5 code metrics you need to watch <a href="http://bit.ly/aObBy8" rel="nofollow">http://bit.ly/aObBy8</a> (via @gsempe)</p> <p><i>This comment was originally posted on <a href="http://twitter.com/nitramf/statuses/9619956466" rel="nofollow">Twitter</a></i></p> 5 code metrics you need to watch http://bit.ly/aObBy8 (via @gsempe)

This comment was originally posted on Twitter

]]> By: Oliver Wehrens http://maxheapsize.com/2010/02/23/5-code-metrics-you-need-to-watch/comment-page-1/#comment-4839 Oliver Wehrens Thu, 25 Feb 2010 08:41:49 +0000 http://maxheapsize.com/?p=459#comment-4839 @Mats, Ah the Typo, no post without it, I fixed it. I can define the time between bug/feature and fix/implementation. A Bug is reported and the bug is closed in the bug tracker. Pretty easy ? Sure you will have multiple of these, each for one severity like critical, blocker and so on. Use the API of your bug tracker to get it ;). That metric tells me if I'm still in my SLA. Same for a feature. If the business analyst takes the time to describe the feature, it must be worth it. So whenever he switches to status 'ready for implementation' we count the time. If it turns out that several features sit around and do nothing we need to look at them and analyze why nothing happened and how we can prevent wasting time of the BA because if they did not get implemented for so long, chances are all the things around changed already and we need to rewrite anyway. But you are right, we are just starting to have a look at those. We are doing agile development if this helps explain why we do look into these metrics. Why do you think cyclomatic complexity is a pretty bad metric ? Just because of long switch statements ? Any more reasons ? @Mats, Ah the Typo, no post without it, I fixed it.

I can define the time between bug/feature and fix/implementation. A Bug is reported and the bug is closed in the bug tracker. Pretty easy ? Sure you will have multiple of these, each for one severity like critical, blocker and so on. Use the API of your bug tracker to get it ;) . That metric tells me if I’m still in my SLA.

Same for a feature. If the business analyst takes the time to describe the feature, it must be worth it. So whenever he switches to status ‘ready for implementation’ we count the time. If it turns out that several features sit around and do nothing we need to look at them and analyze why nothing happened and how we can prevent wasting time of the BA because if they did not get implemented for so long, chances are all the things around changed already and we need to rewrite anyway. But you are right, we are just starting to have a look at those.
We are doing agile development if this helps explain why we do look into these metrics.

Why do you think cyclomatic complexity is a pretty bad metric ? Just because of long switch statements ? Any more reasons ?

]]> By: Mats Henricson http://maxheapsize.com/2010/02/23/5-code-metrics-you-need-to-watch/comment-page-1/#comment-4835 Mats Henricson Thu, 25 Feb 2010 08:05:19 +0000 http://maxheapsize.com/?p=459#comment-4835 OK, here is a question: Have you tried all of these metrics? I mean ALL of them? I think not, because at least one of them is of dubious value (mean time between bug and fix - I bet you can't even define it!). But a good thing with your article is that you have consistently misspelled cyclomatic complexity, which is good, because I think it is a pretty bad metric, so now you've potentially confused Google so badly that no more people can find it on the net. I suggest "Essential Complexity" as its replacement, since it will, for example, not give high numbers for a long, but simple, switch statement. OK, here is a question: Have you tried all of these metrics? I mean ALL of them? I think not, because at least one of them is of dubious value (mean time between bug and fix – I bet you can’t even define it!).

But a good thing with your article is that you have consistently misspelled cyclomatic complexity, which is good, because I think it is a pretty bad metric, so now you’ve potentially confused Google so badly that no more people can find it on the net. I suggest “Essential Complexity” as its replacement, since it will, for example, not give high numbers for a long, but simple, switch statement.

]]> By: gsempe http://maxheapsize.com/2010/02/23/5-code-metrics-you-need-to-watch/comment-page-1/#comment-4813 gsempe Wed, 24 Feb 2010 21:14:18 +0000 http://maxheapsize.com/?p=459#comment-4813 <p>5 code metrics you need to watch <a href="http://bit.ly/93q6bZ" rel="nofollow">http://bit.ly/93q6bZ</a> # programming /thx @sara_broca for the link</p> <p><i>This comment was originally posted on <a href="http://twitter.com/gsempe/statuses/9592913263" rel="nofollow">Twitter</a></i></p> 5 code metrics you need to watch http://bit.ly/93q6bZ # programming /thx @sara_broca for the link

This comment was originally posted on Twitter

]]> By: somesi http://maxheapsize.com/2010/02/23/5-code-metrics-you-need-to-watch/comment-page-1/#comment-4811 somesi Wed, 24 Feb 2010 19:21:03 +0000 http://maxheapsize.com/?p=459#comment-4811 <p>5 métricas de código <a href="http://bit.ly/cfOTal" rel="nofollow">http://bit.ly/cfOTal</a> que nos vienen bien para nuestra siguiente mejora en desarrollo</p> <p><i>This comment was originally posted on <a href="http://twitter.com/somesi/statuses/9588793234" rel="nofollow">Twitter</a></i></p> 5 métricas de código http://bit.ly/cfOTal que nos vienen bien para nuestra siguiente mejora en desarrollo

This comment was originally posted on Twitter

]]> By: links for 2010-02-24 | sashidhar.com http://maxheapsize.com/2010/02/23/5-code-metrics-you-need-to-watch/comment-page-1/#comment-4798 links for 2010-02-24 | sashidhar.com Wed, 24 Feb 2010 09:03:17 +0000 http://maxheapsize.com/?p=459#comment-4798 [...] 5 code metrics you need to watch ¬´ maxheapsize.com (tags: code metrics programming) [...] [...] 5 code metrics you need to watch ¬´ maxheapsize.com (tags: code metrics programming) [...]

]]>