Matt and Mike explore the messy, but inevitable, topic of technical debt. Developing the "correct" way is often less efficient and less immediately satisfying, but it can avoid a potentially insurmountable mountain of spaghetti code later.