Episode 52: The Two-Clock Problem

Isaac and Jeffrey discuss the 'two clock problem' as a metaphor for software rewrites. They explain that adding a new system doesn't improve understanding if you don't know how the current system is wrong. They also emphasize that rewriting a system without understanding the current system is costly and may not be worth it. Instead, they suggest spending more time understanding and documenting the current system to mitigate the need for a rewrite. Takeaways - Adding a new system doesn't improve understanding if you don't know how the current system is wrong. - Rewriting a system without understanding the current system is costly and may not be worth it. - Spending more time understanding and documenting the current system can mitigate the need for a rewrite. Chapters 00:00 Introduction and the Two-Clock Problem 03:09 The Challenge of Understanding the Current System 06:56 The Cost-Effectiveness of Gradual Improvement 08:20 Mitigating the Need for a Rewrite