@PeterLudemann I agree. That's why I advocate to bias toward fixing in-place: in one scenario, that's the right thing to do even though you're not initially sure, in the other scenario, you end up learning from the code you're going to replace so the replacement does a better job. If you write the replacement without benefiting from the experience embodied in the existing code, you're starting from the same place as the people who wrote the original code, and you'll get a similarly bad result.
=> More informations about this toot | View the thread | More toots from jbqueru@fosstodon.org
=> View PeterLudemann@mathstodon.xyz profile
text/geminiThis content has been proxied by September (ba2dc).