Comment by hnfong
2 years ago
If you choose the right frameworks which have sufficient momentum to last you say 10 years, you don't have to put yourself in the dilemma.
And yes, 10 years is quite possible these days. Besides the infamous Javascript framework churn, things are moving quite a bit slower in recent years.
> Besides the infamous Javascript framework churn
reactjs came out in 2013, so it meets the 10y metric, but it has some internal churn, such as classes, hooks, etc
“If you choose the right frameworks” is a big if. Even within a framework, there is versioning and dependency management to account for. Consider the log4j vulnerability. The cost and risk of patching something untouched for 10 years is higher than something touched more recently.
In part, this is due to the risks inherent to change have been spread out over 10 years instead of backloaded to the end.
Practicing mitigating risks by proactively taking them has value of its own. The parable of ergodic cakes shows this.[0] What % of cakes will fail if 10 people each bake one, versus one person baking 10 over time?
https://luca-dellanna.com/what-is-ergodicity/