[vaughandroid]

I'm not a fan of this post as it seems to be pointing the blame at the wrong thing: the problem isn't the shiny new thing, it's the environment that allowed the situation to develop: people working in isolation, key decisions being made by individuals in private, lack of oversight.

There are plenty of arguments in favour of allowing teams to use shiny new tech. Done responsibly, it can help with engagement, job satisfaction, retention, and recruitment.

[borracciaBlu]

I've been witness of developers not working in isolation, with clear specs and requirements, who knew what was the expectation and still use the tech they preferred.

I would say they were unprofessional and selfish. Not great as cultural fit neither.

Discipline should came first. Imagine you go to a restaurant and order a pizza and instead you receive sushi just because the chef wanted to learn a new cooking style..

[Cthulhu_]

But, as a company you should also focus on your own bottom line - working, stable, predictable, reliable software, a codebase you can still hire people for ten years down the line.

Java and C# are safe bets. It probably won't get you the hip polyglot hype developer type, but I'm not convinced there's any company that thrives on those. Maybe for the POC or MVP, but long term you need a reliable tech stack.

I mean take Google; their backbone is/was C++ and they're moving towards Go, which is even more boring than C++ is.