The future proofing of a codebase from the article is IMHO wrong. This is another form of tech debt as you'll get it wrong almost all the time and it will gener

The future proofing of a codebase from the article is IMHO wrong. This is another form of tech debt as you'll get it wrong almost all the time and it will generate dead code or arcane hacks to make it fit for the actual reality. The way to proceed here is to fix the architecture when you spot a discrepancy between the current architecture and the current feature you are trying to implement (not more, not less). The cost is low at that point, later when a dozen features get added in the same manner the cost to fix it becomes too high to swallow.