This is really another good piece and and full of really great examples. I think I’ve been there in a couple of times when I was scaling the companies I’ve been working in all my career.
The main problem here is realising when to choose your battles because there’s always going to be something in the team and especially if you’re an engineer, you’ll find a piece of code, a piece of process always need some kind of improvements.
That’s probably the single most important piece of advice and experience here is that when to choose your battles. This is also a really good sign of being a senior and impactful mature engineer.
More to read:
Mahmut Canga 
What do you think?