> 39. I never use the phrase “future proof” when referring to my work.
> Future-proofing is “100% a fool’s errand”. “You can’t pre-solve problems you have no information of.”
You can't pre-solve problems you are unaware of but in most software engineering two problems are very predictable:
1. The system will have to handle more load in the future.
2. Someone will eventually want to change the business logic.
It is wise to write software in a way that you are well positioned to resolve those problems as they arise. When I use the word future-proofing in my day to day work, this is what I am referring to.
You can't pre-solve problems you are unaware of but in most software engineering two problems are very predictable:
1. The system will have to handle more load in the future. 2. Someone will eventually want to change the business logic.
It is wise to write software in a way that you are well positioned to resolve those problems as they arise. When I use the word future-proofing in my day to day work, this is what I am referring to.