4 ms·
> Edit: Also making it easy to change code when requirements change doesn't mean adding all kinds of generic abstractions to your code. It mean keeping code cle
by toast0 4y ago
> Edit: Also making it easy to change code when requirements change doesn't mean adding all kinds of generic abstractions to your code. It mean keeping code clean and simple and avoiding implicit logic dependencies enough to make code changes easy. Adding a lot of generic abstractions can make it harder to change things instead of easier.
Exactly, when you have two parts of your system that do the same thing but for different reasons, when one of them gets a new requirement, you'll be in a better place with code that was previously redundant than if both places called into a single implementation.