|visits||member for||3 years, 2 months|
|seen||Dec 5 at 16:00|
|bio||website||eksisozluk.com||visits||member for||3 years, 2 months|
|location||Istanbul, Turkey||seen||Dec 5 at 16:00|
How to determine the priority and severity of a “code improvement”?
I agree with points given but I also think there are cases where preemptive improvement gets you broader and longer term benefits for the remaining work on the project. I was aiming for a solid methodology to distinguish those from useless refactoring other than sole intuition. I'm accepting this as the answer because it's a down-to-earth and analytical approach. But I'll still be thinking about that for a while I guess.