Is writing code you won't hate tomorrow a hopeless pursuit? Well, yes, but also no. We have talked about improving the quality of our code, but can we also improve the solutions we are building? Let's explore why we are constantly solving the wrong problem, what Debt actually means, and what we can focus on today to ensure we are around to fix tomorrow's problems.

This talk will incorporate pieces from my previous talks, such as object calisthenics, aspects of growing as an engineer, and learning and experience. But we will add a third layer: understanding business value and why code that never shipped is worse than bad code. The most perfect code we can deliver is the one that allows you to be here to pay that debt tomorrow and try once more to solve tomorrow's problems.