Search code examples
resourcesbug-trackingtechnical-debt

Do you employ any tools for managing technical debt?

The site I work with on a day-to-day basis has its share of shortcomings and we often make design decisions to "get us by right now" with the intention of fixing those up later.

I've found that making the time to actually go back and fix them, let alone remembering what the full list of to-do items is can be challenging at best.

Can you recommend any tools, resources or tricks that help you effectively manage your technical debt?

Solution

  • You could use any bug/task tracking software, eg see this stack overflow question: https://stackoverflow.com/questions/101774/what-is-your-bug-task-tracking-tool.

    Of course, a simple solution is just to have a text file called TODO or similar. It's low maintenance, and particularly appropriate if it's a WORN file (write once, read never).