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.
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.
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..
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.