> Do you want the developer to spend months moving the code from one legacy API to a new one If the situation demands it I would say yes. I treat it as one big

> Do you want the developer to spend months moving the code from one legacy API to a new one If the situation demands it I would say yes. I treat it as one big refactoring job. There are lots of shims in old software libraries that may not need to be there anymore. There are also lots of vulnerabilities that a fresh set of eyes and a different perspective can illuminate. A product that began its life being developed by a lone developer may have an entire team now. The rewrite is a good opportunity to explore how it works and why certain decisions were made.