You're missing one side of the equation. Some of those technical decisions matter a great deal. Some don't, but language and tooling choices affect careers. If we (at hypothetical company X where I work at a given time) become a Spring/Hibernate/POJO/VibratorVisitorFactory hellhole, there is no place for me. Over time, that means that I don't have a job. So, damn right, I am personally invested in fighting that garbage before it gets in. Same when it comes to that trendy "Agile"/Scrum shitshow.

Am I going to tell a front-end engineer with 15 years of exprience that he has to use PureScript because I, personally, think JavaScript is a poorly-designed language? No. That would be dogmatic. I generally prefer letting domain experts call the shots that affect them. It's about getting the right decision, regardless of whether it's my decision, and I may not have all the information.

There are times to step back and let someone else call the shots, and there are times to stand your ground and fight. Make no mistake, though: promotions and demotions and firings result from these decisions and their long-term consequences, so getting them right really matters.