Don't take offence, but reading this it sounds like you're about half of the problem ;) Your team either needs to better separate areas of work, so that you do

Don't take offence, but reading this it sounds like you're about half of the problem ;) Your team either needs to better separate areas of work, so that you don't step on each other's feet all the time and each coder has a bit more freedom of how to solve problems, or you need to sit down and agree on a number of fundamental coding style and 'architecture' rules that everybody needs to follow. Apart from the organisational and trust issues (which I think are the main problem here), tools like clang tidy, clang format, ASAN, UBSAN, TSAN, a CI pipeline and automated profiling/benchmarking can help to bring in some more 'objectivity' into discussions.