2 ms·
Sure, you can absolutely write a new program with the same feature list instead of more closely porting the old logic over to the new language. But now you hav
by smacktoward 10y ago
Sure, you can absolutely write a new program with the same feature list instead of more closely porting the old logic over to the new language.
But now you have a new problem: a Chesterton's Fence (https://www.chesterton.org/taking-a-fence-down/ https://www.chesterton.org/taking-a-fence-down/) problem. The old logic is in the form it is (knotty and complicated, most probably) because previous developers made it that way in response to problems they were facing at the time -- problems you may not be aware of, because their old changes made those problems go away. Those knots represent places where those previous developers learned that the problem they were trying to solve wasn't as simple as it first appeared.
You can definitely simplify the porting job if you just ignore all that and write new logic that does The Simplest Thing That Could Possibly Work, but by doing so you can set yourself up for future heartburn as all those forgotten edge cases come roaring back. You end up re-learning the hard way lessons your predecessors learned the first time around.