[ntuandung93]

People here have already given good advice how to deal with product owners/managers. So I'm rather going to talk about the root, which is how to deal with technical debt in the first place.

As a developer myself, I know it's hard to review the Pull Request with good insight just by looking at the diff. What I want to say is that we sometimes might neglect some technical debts by not understand fully the high-level overview of the Pull Request. So in order to avoid that, you and your fellow devs might want to spend more times to review Pull Request and talk about the technical debt that will be introduced by those PRs. This will vastly reduce the amount of debt you have to pay later in my opinion.

Apart from improving it in a normal way, there's a tool for that called Softagram. What it does is that for every Pull Request you made it will analyze your PR and then post a comment with high-level overview graph (or picture) about that PR directly to your PR thread. So that it's much easier to discuss with your fellow devs about what decisions you should make regarding the technical debt. As a result, the process of reviewing PR is much more enjoyable, faster, and more secure. You can check out the tool at https://softagram.com

[totall77]

In the ideal world that's how it should be, in every pull request, the reviewers should check the architecture and implementation to fix issues increasing the debt. Instead to be fixed later with 10-100x costs.

[ntuandung93]

Hi, thanks for your thought. You might want to checkout how Softagram can help you here: https://www.youtube.com/watch?v=_3OzOVIOmkQ&feature=youtu.be