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.
Watch on YouTube or listen to it at NeverRewrite, Spotify, Apple Podcasts, or Amazon Music, and let us know if you have ever been involved in a rewrite. We would love to have you on the show to discuss your experience!
