NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
an endless discussion thread about what features to include.
-- Jarkko Hietaniemi
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
I'd feel sad... (Score:1)
... that they feel the need to stick it up as a separate card rather than doing continual refactoring. I'd want to work with them on that :-)
Adrian
Re: (Score:1)
What if you suddenly wake up an realize you have a large volume of duplicated test code (which may be the case, I have no idea)? Wouldn't you want to schedule time to make a serious difference?
I think the presence of a card is a very un-sad thing for various reasons (they identified the problem, took action, got on scheduled time for it).
Re:I'd feel sad... (Score:1)
Yes. You're right. I was obviously feeling especially grumpy when I wrote that. The presence of the card is certainly a good sign that folk are paying attention to the code and know improvements need to be made. Yay :-)
That said - I've seen too many folk who get into this nasty cycle of hack-code-until-mud... oh bugger.... better write some refactoring cards.... spend time persuading product owner than they really, _really_ need to do the refactoring cards.... refactor.... hack-code-until-mud... repeat...
Refactoring should be continual. That's when you start getting real benefit. So I would see the card as a good sign - but also a sign that things could get better.
Reply to This
Parent