> ... that is much cheaper on the long run.
> If it's that case that it is cheaper, and even then people above you do not want the change, then you do have a real problem.
Not necessarily so. This assumes the long run is ever reached. I've seen a lot of developers that do this analysis still hop from tech to tech as the best in "the long run", and if you ever listened to them you would never actually reach that long run benefit.
Regardless, a lot probably depends upon the current state of your company.
- Your stack is bad.
- You should use X.
- Your process is wrong.
A sure way to sound like an experienced senior developer:
- Your stack has this flaw; we can live with it by doing X but that is at the expense of Y1. A migration to Z will cost Y2, that is much cheaper on the long run.
But you'll probably conclude that Y2 isn't much cheaper on the long run anyway. If it's that case that it is cheaper, and even then people above you do not want the change, then you do have a real problem.