News for hackers. Stuff that matters.

A comment on Avoid rewriting a legacy system from scratch by strangling it. Parent comment

Re:Avoid rewriting a legacy system from scratch by stranglin... by ericmcer on Tuesday February 18, 2020 @01:30AM (#22353933)
I am in a similar position. We started the strangling process 2 years ago but due to management not wanting to disrupt old clients by shifting them to the new code (same stuff updated UI) the strangling strategy has basically shifted into us maintaining two copies of many feature. Success!
[ Parent | on HN ]
Re:Avoid rewriting a legacy system from scratch by stranglin... by delusional on Tuesday February 18, 2020 @04:03AM (#22354539)
That's the hardest part of any strangulation. The process can not involve any new features. If it does you will never transition everything.
[ Parent | on HN ]
Re:Avoid rewriting a legacy system from scratch by stranglin... by felipellrocha on Tuesday February 18, 2020 @12:42PM (#22358069)
If you're maintaining two copies of the same features, then, by definition, you're not exactly following the process described? The process was developed to avoid exactly that
[ Parent | on HN ]