on top of what akg_67 said (Worry about the things that you can control and ignore the things that you can't control.) I need to add that your story seems to im

on top of what akg_67 said (Worry about the things that you can control and ignore the things that you can't control.) I need to add that your story seems to implicate you do not have a way to measure the efforts put into your code, quality assurance is one you can use and it's quite well known. In the teams I've been part of and managed, egos always tend to come into play when writing code: I got better ideas, I got better line indenting, blah blah... been there, done that. I think it's mostly important to focus on the outcome: practically speaking the way I would tackle this is by introducing some level of QA, either by introducing TDD or else. You start by writing tests as use case scenarios, and then implement the code. Once this is done, if any of your colleagues wants to re-implement the code/module/whatever, let them do it, but the tests need to pass and the improvement should be measurable. Otherwise who f*ing cares? Peace!