3 ms·
Incremental rewrites (aka refactoring) is best, but sometimes that's just not viable, which is where I feel conventional wisdom breaks down. If your code is tr
by ergothus 7y ago
Incremental rewrites (aka refactoring) is best, but sometimes that's just not viable, which is where I feel conventional wisdom breaks down.
If your code is trying to get updated, you can usually refactor. If your code is having a paradigm shift, it's likely any incremental rewrite will take more time and have more duplication without benefit for far too long to be successful.
- s_y_n_t_a_x 7y agoIncremental rewrites !== refactoring. You can rewrite portions of the app and embed the older components in the new app until you rewrite them as well.
- dragonwriter 7y ago> Incremental rewrites (aka refactoring) Refactoring is recoding a component while maintaining it's external interface so that external interactions with the component are unaffected. Rewrites, incremental or otherwise, do not necessary preserve external interfaces (an incremental rewrite doesn't start clean slate, but instead progresses by gradual replacement of existing code. The two ideas are not closely connected.