*At what point is it more economical to throw away a module and write a replacement instead of refactoring or extending the module to meet new needs?*
If you have rotation in the team it is a lot easier to get new people write new code than learn old ways - especially when original authors are all gone.
If you have stable team, as long as knowledge is there and module fits style of the team I think rewrite will not be needed unless someone wants to shove some not fitting requirements there, which would be better handled by just making separate module.
If you have rotation in the team it is a lot easier to get new people write new code than learn old ways - especially when original authors are all gone.
If you have stable team, as long as knowledge is there and module fits style of the team I think rewrite will not be needed unless someone wants to shove some not fitting requirements there, which would be better handled by just making separate module.