We use multiple things. * We do code reviews and inline/trello todos. If we're on a tight schedule, this helps us remember why and what needs to be reworked.

We use multiple things. * We do code reviews and inline/trello todos. If we're on a tight schedule, this helps us remember why and what needs to be reworked. * When adding new features we use regular development cycle (spec, design, review, develop, test, finish), but we also add one more process before finishing that is focused on improving todos from previous cycle. The reasoning is that after todos have been sitting there for a while, you might look at them a bit differently and while something wasn't as obvious back then it might become now. Refactoring matters a lot to us. We don't overdo it however and dedicate 1-3 days to it from the cycle. * If any major/breaking version of react/django/drf comes out, we pause and update the tech stack. Run tests and fix any issues. * If any major bug that hinders the users experience occurs we allocate resources in parallel with the current dev cycle. * Update the documentation early and often. * Write tests. Tests force you to kill the debt before it happens. We have much better unit test coverage than integration test coverage for our front-end.