I think you're correct to recognise obvious problems like mongodb and yaml etc In your time you would have seen more reliable solutions to the same problems T

I think you're correct to recognise obvious problems like mongodb and yaml etc In your time you would have seen more reliable solutions to the same problems The reality is that good teams can make good products and codebases with a bad stack, yes certainly hampered but still good It's ignorant to think your point of view should be the only one of merit, in a team you have to consider the developers who want to use mongodb As the senior on the team you should be on board with your team and try your best to steer your team away from foot guns I don't think it's enough to say X is bad without having used X long enough to really know how and when things will break down Otherwise you might just be labelled the grumpy old man on your team who hates everything, your team need to trust your opinions based on genuine experience Based on what you've written so far I would not respect your opinion on much outside of Java My advise is that you need to earn the trust and respect of your team when it comes to talking about new tech