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 -

Method	Cyc. Compl.	LOC	Blank lines	Comment lines	Comment %	Statements
GenMoves	50	437	23	114	26.09	236
FENToPosition	41	117	18	27	23.08	99
IsAttacked	26	193	17	74	38.34	102
PieceToString	16	21	0	0	0.00	32
ColourOfPiece	14	16	4	0	0.00	4
PieceToString	10	15	0	0	0.00	20
HitTheEdge	10	31	9	0	0.00	10
ASCToFEN	9	53	6	19	35.85	26
FirstBit	8	39	10	0	0.00	21
MoveToString	8	28	1	0	0.00	17
Slide	5	25	6	4	16.00	15
GetMoveCount	4	21	6	0	0.00	12
PrintMoveList	2	5	0	0	0.00	2
LeftEdge	1	4	0	0	0.00	2
RightEdge	1	3	0	0	0.00	1
TopEdge	1	3	0	0	0.00	1
BottomEdge	1	3	0	0	0.00	1
SquareToString	1	3	0	0	0.00	1
SquareToString	1	3	0	0	0.00	1
SquareToRank	1	3	0	0	0.00	1
SquareToFile	1	3	0	0	0.00	1
ASCToPosition	1	3	0	0	0.00	1
Warn	1	3	0	0	0.00	1

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

• why do four of the complex methods have no comment lines at all?
• Why is FENToPosition so complex? (this was a surprise)
• Is Slide() under-commented at 16%?
• What (if any) is the correlation between lines of code (LOC) and Complexity?
• Is this consistent with other code I've written?
• How do all these stats compare to other projects?
• Does this align with my intuitive sense of their complexity?
• Is there a code density metric I can derive from LOC and statements?

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.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.