3 ms·
On the flip side, change is far more risky when it affects many callers rather than once page. Whatever time you “wasted” fixing multiple pages might be instead
by hamandcheese 4y ago
On the flip side, change is far more risky when it affects many callers rather than once page. Whatever time you “wasted” fixing multiple pages might be instead spent validating that the single fix doesn’t produce any unintended consequences.
Simple duplication is probably the least bad form of tech debt I can imagine.
- iopq 4y agoYou have to test all of the affected pages anyway the real horror is they have slightly different version since they already had other changes done to them, and I have to understand whether I should merge the functionality, keep it different, etc. when I have multiple callers it's going to be the same unless you pass in an argument, so that change is self-documenting since it signifies intent