I think a huge part of the shiny tech proliferation comes from the pseudo-agile movement. Usually pseudo agile means one thing: no spec. You get a team tell th

I think a huge part of the shiny tech proliferation comes from the pseudo-agile movement. Usually pseudo agile means one thing: no spec. You get a team tell them "let's do this widget" with no detail, no edge case scenario, no perf requirement. So they choose last awesome tech which solution a problem they got last time and will look good on a resume. And only after a month or two of making things do the real hurdle of this tech start appearing. All the things you never see mentioned in those "let's get started" tutorials or shiny-techs online conference. With some time spent thinking about the problem space and what happen when things go bad your team could have sensed that nothing is all sugar and rainbows. Take micro services: at first it looks elegant. But when you start thinking about how to manage transactions for some actions across multiple services or how to handle some of your server dying then coming back to life you suddenly have the urge to stop and check if you really need this kind of architecture at first.