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 497608
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: obsession with data
by Slambert666 on Fri 18th Nov 2011 08:05 UTC in reply to "RE: obsession with data"
Slambert666
Member since:
2008-10-30

Probably not fired for "not using the system" but probably for being difficult to manage (as in making the managers job difficult).
Many companies tends to frown upon that, just so you know....

Reply Parent Score: 2

RE[3]: obsession with data
by senshikaze on Fri 18th Nov 2011 17:23 in reply to "RE[2]: obsession with data"
senshikaze Member since:
2011-03-08

While you are absolutely right, I would rather not fall in line and go along with the rest of the people in the cubicle farm.
Make waves, all the interesting people do.

Reply Parent Score: 1

RE[3]: obsession with data
by looncraz on Sat 19th Nov 2011 01:32 in reply to "RE[2]: obsession with data"
looncraz Member since:
2005-07-24

Probably not fired for "not using the system" but probably for being difficult to manage (as in making the managers job difficult).
Many companies tends to frown upon that, just so you know....


Yes, I was fired for a combination of reasons - they were listed (verbally):

1. Failing to use required tools
2. Management didn't like you because you didn't use the required tools and they couldn't monitor you
3. Complaining that the workflow required 3 monitors
4. Complaining about Internet Explorer 6's slow performance and lack of tabs


In the end, though, only ONE manager did any complaining (I had six... and was, myself, a 2nd level manager...LOL!) - and only because I was deemed a threat to his might. Co-workers complained and he was relocated and I was -eventually- offered my job back, which I didn't take.

Always more to the story ;-)

--The loon

Reply Parent Score: 2