I agree with the first bit; however it's hard to find a balance between accepting that your code can be improved, and standing by your solution. What I see in m

I agree with the first bit; however it's hard to find a balance between accepting that your code can be improved, and standing by your solution. What I see in my team is that someone else has another solution, and whatever that is, should be implemented, if you argue against it, then it's often "I'm just trying to improve your code". However his solution might not necessary be better, it's just a different approach. We also follow very strict style guides, but this is all defined in formatters and linters, so there's no arguing against it. Even for my personal projects, the first thing I do is usually set up .editorconfig and TSLint (if I use Typescript).