There is a middleground.
Of course, change for the sake of change sucks, you just have to relearn for no benefit.
But change for the sake of implementing m
New features and having a well thought out redesign after collecting issues over a decade or so makes software more accessible and allows you to streamline workflows where new features just got tacked on over time.
But change for the sake of implementing m New features and having a well thought out redesign after collecting issues over a decade or so makes software more accessible and allows you to streamline workflows where new features just got tacked on over time.