> The basic problem of our world is that it is ruled by 20-sometings that loath working on "old" tech. disagree completely, it's not the 20-somethings that com

> The basic problem of our world is that it is ruled by 20-sometings that loath working on "old" tech. disagree completely, it's not the 20-somethings that come to you and say "the budget we have is limited, and we have to prioritize, feature X might get us more exposure, so work on that and it doesn't matter if it breaks backwards compatibility, users will adapt" If upper mgmt goes after "oh shiny" there's not you can do at the individual contributor level, and if you know you are in a "oh shiny" management situation there is also no incentive whatsoever in spending time making sure you think about the future when developing, since you're going to have to throw everything away anyways in a few months or a year at the most. It's all about "being nimble" and "velocity" and "being innovative", where all of them are more or less shorthands for "churn things quickly until something sticks". Stable, reliable, dependable software is unsexy, if the company you work for is large enough you might be able to find a team that works along those lines and be happy, otherwise it's fighting fires all the time.