Hey Ignacio! Thank you for your question. Tech debt not always occurs due to incompetence. One of the most popular way of categorizing debt comes from Martin Fowler’s Technical Debt Quadrant who suggested the following types:

- Reckless and Deliberate

- Reckless and Inadvertent

- Prudent and Deliberate

- Prudent and Inadvertent

If the debt is 'reckless and accidental' the company should invest resources into training the people who create it, establish coding standards, and have better code reviews. Because if the team member is shipping too much accidental and reckless debt, moving them will just mean moving the debt to another part of the codebase.

If you'd like to learn more about it, I'd recommend this article https://www.stepsize.com/blog/complete-guide-to-technical-debt

Let me know if it's helpful!

Building Stepsize, a SaaS company to measure and manage technical debt.

Love podcasts or audiobooks? Learn on the go with our new app.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Alex Omeyer

Alex Omeyer

Building Stepsize, a SaaS company to measure and manage technical debt.

More from Medium

“500 Internal Server Error” on Lumen after deploy

CS373 Spring 2022: Sahran Hashim

CS373 Spring 2022: Yifan Zhou

Configure Application Auto Scaling to manage Lambda provisioned concurrency on a schedule