Like usual, our society operates in extremes. When I first came into tech businesses would use old, cumbersome stacks because refreshing every 5 years was of no

Like usual, our society operates in extremes. When I first came into tech businesses would use old, cumbersome stacks because refreshing every 5 years was of no benefit to business oriented people. A good chunk of businesses (still) don't really like the word refactor, so they don't integrate a certain percentage of it into the roadmap. Then engineers got tired of maintaining software that was on life support without acknowledgement, and the competition for engineers took over. Now you have incredibly new relatively untested stacks and tech being used as a recruitment tool. This might be my personal opinion, but if you write modular code and dedicate about 40% of your roadmap to refactor, commiting code upstream, and engineering related tasks you won't run into near as many long term maintainability issues.