@jbqueru When I've replaced legacy code, half the time I should have fixed it instead; and when I've fixed legacy code, half the time I should have replaced it. (In both cases, adding tests of course).
If I had made the opposite decisions, I probably would have concluded that I was mistaken the same 50-50.
Bad code is like a cancer - all remedies are bad and it's a matter of guessing the least bad cure. (And the author of the bad code probably got promoted before the effects of that code manifested.)
PS: bad design is even more problematic.
=> More informations about this toot | View the thread | More toots from PeterLudemann@mathstodon.xyz
=> View jbqueru@fosstodon.org profile
text/geminiThis content has been proxied by September (ba2dc).