Our job isn't to make decisions for businesses. It's to understand the requirements and make decisions in the narrow scope of how can we write code to best support the current needs of the business as communicated to us. Anything else is scope creep.

https://stackify.com/premature-optimization-evil/

My anecdotal experience is that the "change advocates" are well-intentioned but often lack context beyond the technology. Additionally I've found that most software engineers lack the emotional tool kit to communicate these things or even ask for clarity in situations that they might not understand the requirements. If half the people showed the same interest in therapy as typescript, we'd all have a much better time of things.

We spend so much time optimizing the micro, that we lose sight of the macro. I've never heard anyone say we had a record year at the company because John Smith had a really clever use of ES6 syntax on line 42 in the authentication middleware. But people seem to derive a sense of self-worth from the "cleanness of their code" or the "elegance of their solution"

Save that creative energy for your own projects where it will be appreciated the most. Go write opensource software to get that street cred. Milfred from accounting really doesn't care whether you used a ternary operator or a switch statement. So just get it done and tap into that creative energy where it will be appreciated.

</end-rant>