3 ms·
You should never design for the future use case. You don't know what the future will be. You should only design for the current use case you have today and depl
by pkrumins 6y ago
You should never design for the future use case. You don't know what the future will be. You should only design for the current use case you have today and deploy. When the future comes, you return to the code that you wrote and update it to fit the new needs.