> Team is doing OK with the current boring tech stack

> Senior Dev who is chronically on Twitter: "Hey guys, we should adopt this new library, React-TailsbyQL-babelfu by so-and-so Node though-leader because it makes this one very specific pattern easier! Look at how slick the docs look!"

> Team: "But we already swapped that part of our stack a year ago, and that one pattern would only help in a few specific parts of the codebase."

> Senior Dev makes argument to Product Manager

> Product Manager agrees because it'll look good to the rest of the company

> We complete migration to new shiny new tool; 30 transient dependencies and 4 config files added

> Senior Dev and Product Manager boast to other teams about the successful migration and cherry-pick LOC reduction in certain modules, omitting the added configs and complexity elsewhere; other Product Managers are impressed

> Meanwhile the app now performs worse; weird bugs creep up because details are now obfuscated by the new library; new devs now have to learn the codebase + the way this library dictates things must be done

> Devs start paying for courses by the author of said library using continuing education funds because the docs for the library are insufficient

> Author of library deprecates library; moves on to new library that does almost the exact same thing, and starts evangelizing it on Twitter

> Senior Dev comes back "Hey guys, check out this new library..."

You can tell I'm not bitter.