The main gist is whatever you add to the company stack, the company is now responsible to maintain, possibly forever. My current situation is basically this ti

The main gist is whatever you add to the company stack, the company is now responsible to maintain, possibly forever. My current situation is basically this times 10 since the people who did exciting tech left. If the team and managers agree, by all means use the exciting tech, but it isn't a decision to make in isolation. The canonical link on choosing boring technology is http://mcfunley.com/choose-boring-technology http://mcfunley.com/choose-boring-technology. A relevant example is microservices which are all the rage right now. But, you have to be this tall to use them[0]. You cannot effectively just say you are going to do microservices, especially if you don't know how to do microservices. Alternatively, consider the potential problems for your company if you had introduced React on your own in a core business element, and your company had a patent beef with Facebook, and FB hadn't switched to the MIT license. [0]: https://martinfowler.com/bliki/MicroservicePrerequisites.html https://martinfowler.com/bliki/MicroservicePrerequisites.htm...