I've worked with both sides of this argument and I find that "new shiny" is a perpetual problem. Anyone that proposes new shiny should be responsible of showing

I've worked with both sides of this argument and I find that "new shiny" is a perpetual problem. Anyone that proposes new shiny should be responsible of showing trade offs, integration feasibility, impact, etc. I'm not against new technology but so many people want to adopt new technology X just for the sake of it being new technology X. I see this on developer teams I work with every day and it makes me want to gouge my eyes out sometimes, especially when I end up being forced to use their nonsensical choice of new technology X which makes my life harder. Part of the problem I believe is that everyone is focusing on their own self-interest. Many developers for the most part don't care much about the business interests/growth. They're already looking for their next higher paying gig and want paid training in technology X at their current gig. Since many businesses provide little concern for long term talent retition, loyalty or investing in professional development that falls outside their business adopted technology preview, I completely understand the developers choosing themselves over the business. At the same time, going overboard shoots yourself in the foot because it strangles the business in the process. There certainly needs to be a balance and a lot could be gained by giving developers freetime and resources for continued professional development.