Should we treat technical debt like a subscription?

Been noodling on this: What if we treated technical debt like a subscription service instead of a mortgage? Most teams think they're paying down debt, but really they're just refinancing it. Moving it around. Pushing it into different corners of the system. Maybe instead of grand refactoring projects, we need micro-cancelations. Small, constant decisions to stop paying the subscription on certain technical compromises. Just a thought experiment, but it's making me look at our backlog differently...

To view or add a comment, sign in

Explore content categories