The Artima Developer Community
Sponsored Link

Weblogs Forum
Software Metrics Don't Kill Projects, Moronic Managers Kill Projects

50 replies on 51 pages. Most recent reply: May 16, 2008 1:38 PM by Thomas Cagley

Welcome Guest
  Sign In

Go back to the topic listing  Back to Topic List Click to reply to this topic  Reply to this Topic Click to search messages in this forum  Search Forum Click for a threaded view of the topic  Threaded View   
Previous Topic   Next Topic
Flat View: This topic has 50 replies on 51 pages [ 1 2 3 4 5 6 ... 51  | » ]
Alberto Savoia

Posts: 95
Nickname: agitator
Registered: Aug, 2004

Software Metrics Don't Kill Projects, Moronic Managers Kill Projects (View in Weblogs)
Posted: Oct 30, 2007 11:52 AM
Reply to this message Reply
Any software metric can be abused or misused, but does this mean we should avoid any and all software metrics? Joel Spolsky, Eric Sink, and I have an interesting, late night, conversation.

Yesterday (October 29th) I gave a talk on the CRAP metric and Crap4j at The Business of Software conference. Eric Sink and Joel Spolsky were also speaking at the conference.

At the end of the evening, I went to dinner with some of the other speakers and had an opportunity to meet and spend some quality time talking about CRAP and other software metrics with Joel and Eric.

Joel is not a big fan of software metrics in general. He is concerned that developers might end up writing code and allocating their time to satisfy a specific metric rather than writing the best possible code and allocating the time based on more important criteria. He narrated a couple of stories about horrific metrics misuse that he witnessed first-hand and was concerned that - in the wrong hands - the CRAP metric could be used in, say, performance reviews: You code is too crappy. You're fired!

I understand that there is potential, as well as some evidence, for software metrics misuse; but I don't think that's sufficient reason for avoiding metrics altogether. My reply to Joel was that if an organization/manager is so lazy and stupid to rely exclusively on any given code metric in evaluating programmers, then those programmers are probably better off being fired from that organization anyway. Better yet, the programmers would have great evidence to have the moronic manager fired.

While I understand that any tool, technology, or information can be abused by evil people and misused by stupid ones, I don't think we should use "How could this be abused or misused?" as the primary criteria - at least not without first balancing it against the potential benefits.

Toward the end of the conversation, Eric Sink observed that the argument was starting to sound a lot like the perennial "Guns don't kill people, people kill people" discussion. Great observation Eric.

What do you all think about software metrics?

Aren't you a bit surprised that, despite the fact that software runs the world and that we spend hundreds of billions a year writing and maintaining software, there isn't a single industry-wide metric that's being used with any consistency. Why is that?

Are all software metrics inherently evil and useless?

Is programming so much more art than science or engineering that it's pointless to try to quantify or evaluate code using objective criteria?

What do you think? Do you have any software metric horror/success stories to share?


Flat View: This topic has 50 replies on 51 pages [ 1  2  3  4  5  6 | » ]
Topic: Software Metrics Don't Kill Projects, Moronic Managers Kill Projects Previous Topic   Next Topic Topic: Thinking in Java 4e

Sponsored Links


Copyright © 1996-2018 Artima, Inc. All Rights Reserved. - Privacy Policy - Terms of Use