>> You think you know how to build the new version, but you really don't. Years of improvements of the old version, years of bug fixes, years of business knowledge are below the surface.
This point has always baffled me. The old adage of "if it ain't broke, don't fix it." but then in the past decades of everybody jumping on the JS frameworks and whole heartedly believing by moving to "X" framework, they can eliminate all the issues you have or had with the older version.
In my own experience, it never goes this way. Oh sure, do you want to be working in legacy code that's 10 plus years old? Probably not, but the idea that every new shiny thing has all the answers to all the issues you had before is a sure fire way to get a lot of people fired for overpromising and underdelivering.
This point has always baffled me. The old adage of "if it ain't broke, don't fix it." but then in the past decades of everybody jumping on the JS frameworks and whole heartedly believing by moving to "X" framework, they can eliminate all the issues you have or had with the older version.
In my own experience, it never goes this way. Oh sure, do you want to be working in legacy code that's 10 plus years old? Probably not, but the idea that every new shiny thing has all the answers to all the issues you had before is a sure fire way to get a lot of people fired for overpromising and underdelivering.