The problem is not you, it's their "opinionated opinions". Normally, the hidden rule is: If you can't prove your opinion, don't say them. If you really need t

The problem is not you, it's their "opinionated opinions". Normally, the hidden rule is: If you can't prove your opinion, don't say them. If you really need to say something, there're two strategies: - Spoil why current approach is not good (with proof). - Give suggestions on how to improve (with proof). Actually, things sometimes got tricky with "proof", because it depends. For example, code style. Normally i always go with simple functions (instead of adding bunch of class methods). Because i found it simpler to test, debug,... The team might disagree and i just don't care much, because everyone should respect how a developer is productive.