Episode Two - Iteratively Replace

In this episode we provide an alternative to rewriting a codebase from scratch: iteratively replacing bits of functionality over time. We share four reasons why iterative replacement is better:

- you get value sooner (every release)
- improvements are locked in. They don’t disappear if the project goes on hold or canceled
- you’re solving problems today, not imagining how you solve them tomorrow
- customers are buying what you’re selling today, not what you will be selling next year

Show notes:

Studies related to frequency and size of commits that Jeffrey mentioned:

https://www.diva-portal.org/smash/get/diva2:1381601/FULLTEXT02
https://link.springer.com/article/10.1007/s10664-022-10257-9

If you’d like to be a guest on our podcast, apply here: https://forms.gle/kTAdW3dMuwJdzBgo6