Skip to main content
Software Engineering

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

8
  • 3
    My money on this answer.. Commented Mar 18, 2013 at 7:42
  • 3
    +1 for excellent answer. You won't end up "gold-plating" code that ends up never being used because requirements changed Commented Mar 18, 2013 at 8:50
  • 8
    On a perfect project with perfect management and a team of uniformly great developers this answer would stand. Unfortunately I have never seen or heard of such a project in my ten years in the industry. Commented Mar 18, 2013 at 13:14
  • 3
    Try to do this but when you can't (and it will happen due to time pressure or because you simply don't know how to do it right, yet) create a ticket in your ticket system. This way you can hopefully come back to it while the problem is still fresh in your mind and not only when it eventually starts causing problems. Commented Mar 18, 2013 at 13:42
  • 1
    I think this is good advise, but does not address the question asked. Haivng managed a team with a horrendous code base (was horrendous before I got there). It was time very well spent to tackle refactoring and cleaning up specific functions. We called them infrastructure projects and worked them into every sprint we could. Often these things were items that were not part of another change, but were things the team had identified as problem areas. We did quarterly retrospectives and would update this list regularly. Commented Mar 18, 2013 at 14:19