Linked by snydeq on Thu 17th Nov 2011 22:47 UTC
General Development Fatal Exception's Neil McAllister discusses why code analysis and similar metrics provide little insight into what really makes an effective software development team, in the wake of a new scorecard system employed at IBM. "Code metrics are fine if all you care about is raw code production. But what happens to all that code once it's written? Do you just ship it and move on? Hardly - in fact, many developers spend far more of their time maintaining code than adding to it. Do your metrics take into account time spent refactoring or documenting existing code? Is it even possible to devise metrics for these activities?" McAllister writes, "Are developers who take time to train and mentor other teams about the latest code changes considered less productive than ones who stay heads-down at their desks and never reach out to their peers? How about teams that take time at the beginning of a project to coordinate with other teams for code reuse, versus those who charge ahead blindly? Can any automated tool measure these kinds of best practices?"
Thread beginning with comment 497649
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: obsession with data
by Alfman on Fri 18th Nov 2011 18:57 UTC in reply to "RE: obsession with data"
Alfman
Member since:
2011-01-28

looncraz,

Yep, instead of recognizing your good work, some bean counter had to justify their job by firing you even if it hurt the origination as a whole.

I too have been fired, but it was for the incompetence of another full time developer who found it beneficial to point the finger at me as a scape goat to the management. They paid me less than half of what they owed. That small company is no longer in existence.

I agree with Yamin that developers can usually recognize each other's strengths and weaknesses, but we also live in a time when politics are needed to get ahead and stepping on each other is often better rewarded than hard work. I don't think there is any possible combination of metrics that would fix this.

Reply Parent Score: 1

RE[3]: obsession with data
by Yamin on Fri 18th Nov 2011 21:27 in reply to "RE[2]: obsession with data"
Yamin Member since:
2006-01-10

I'd just add for emphasis, developers should not just be 'analyzed' by other developers, but by all people in the organization. Testers, product managers, customer support, sales, other groups...

Working in a large organization is complex and hard work or talented work is not all that matters.

Reply Parent Score: 3