I think that the main problem boils down to having common understanding what does "managing the tech debt" mean across the dev team. I know some people that are totally overzealous about it and are very debt averse, similar to people who will never take a mortgage. While this approach is better than just accumulating debt, it's also not …
I think that the main problem boils down to having common understanding what does "managing the tech debt" mean across the dev team. I know some people that are totally overzealous about it and are very debt averse, similar to people who will never take a mortgage. While this approach is better than just accumulating debt, it's also not optimal.
There is a point at which accumulating technical debt might be a result of taking calculated risks and making trade-offs for faster time-to-market, thereby increasing the overall sense of achievement and morale within the team. Personally, I find lack of tech debt to be just another smell and sign of possible premature optimization.
A huge part of it is also affected by how well the team understands business goals and their proximity to the product/business. If you have a good understating about what's important, you won't push to fix that part of code that works and is not subject to change in the foreseeable future.
I think that the main problem boils down to having common understanding what does "managing the tech debt" mean across the dev team. I know some people that are totally overzealous about it and are very debt averse, similar to people who will never take a mortgage. While this approach is better than just accumulating debt, it's also not optimal.
There is a point at which accumulating technical debt might be a result of taking calculated risks and making trade-offs for faster time-to-market, thereby increasing the overall sense of achievement and morale within the team. Personally, I find lack of tech debt to be just another smell and sign of possible premature optimization.
A huge part of it is also affected by how well the team understands business goals and their proximity to the product/business. If you have a good understating about what's important, you won't push to fix that part of code that works and is not subject to change in the foreseeable future.