Everyone has technical debt. The question is what to do with it.
Refactor now? Wait for the next feature? Build on it and hope it holds?
This session is about the real-life trade-offs teams make every day:
- How to decide what debt is worth paying - How to talk about debt with business stakeholders - How to stop fixing code that should have been rewritten, or retired
If you’re tired of debating whether to clean up or move on, this session helps you frame the debt conversation in a way that supports both speed and stability.
