http://qs1969.pair.com?node_id=421562


in reply to Re: Cyclomatic Complexity of Perl code
in thread Cyclomatic Complexity of Perl code

I empathise with your tales of woe, but I think you go too far in dismissing the value of metrics as source code instrumentation.

If one considers a given metric to be part of the whole picture, but at the same time does not confuse the single metric for the whole of the picture, I think metrics can help a great deal, particularly when dealing with large volumes of code, and large numbers of coders, and particularly in terms of informing decisions about where to spend code review and unit test effort.

It sounds like you have suffered from idiotic applications of misguided rules more than you have suffered from the metrics themselves, but perhaps that is the price of their existence; that they will be abused like so much else.

Out of interest, I generated these metrics for a part of my hobby chess engine -

MethodCyc. Compl.LOCBlank linesComment linesComment %Statements
GenMoves504372311426.09236
FENToPosition41117182723.0899
IsAttacked26193177438.34102
PieceToString1621000.0032
ColourOfPiece1416400.004
PieceToString1015000.0020
HitTheEdge1031900.0010
ASCToFEN95361935.8526
FirstBit8391000.0021
MoveToString828100.0017
Slide5256416.0015
GetMoveCount421600.0012
PrintMoveList25000.002
LeftEdge14000.002
RightEdge13000.001
TopEdge13000.001
BottomEdge13000.001
SquareToString13000.001
SquareToString13000.001
SquareToRank13000.001
SquareToFile13000.001
ASCToPosition13000.001
Warn13000.001

As a profile of this part of the engine, I found this very interesting. For instance,

Now some of these thoughts I could have had by simply browsing the code, but I hope I'm illustrating the usefulness of these metrics as a high-level view. I find them provocative in a highly beneficial way.