As a new senior software engineer to a team, I find it very frustrating to push for newer projects to be prioritised in the team's backlog. I often find that resistance comes in two forms:
1) This has been tried before, and need not be attempted (à la "historian's fallacy")<p>2) This is too strategic, and changes systems which are working fine today. We should look for low-hanging fruits.<p>How do you deal with this?