Rod at work - Thursday, January 31, 2019 8:25 AM
I've worked in an environment where the developers (led by one of the company owners) always seemed to be doing two things at once:
If you put in place a process to control the introduction of new tech, perhaps even requiring a well-thought explanation as to *why* TechX will be better / improve things than the current TechY, you can keep your technical debt under control, improve the supportability of your software, and (one hopes) get the developers / managers / etc to actually *think* about why they want TechX. If the benefits are worth it, you start using it. If the only reason to use it is "it's new and cool and all the cool kids are using it" then you shelve the idea.