If I can go through a projects code base and tell you which developers on the team wrote each section of the entire app then you’ve utterly failed as a dev team. You can call that conformity or whatever but that’s what makes code easy to read and maintain. I don’t want to have to read or worse refactor the same problem from 4 different implementations because each dev on the team decided they wanted to do it their way.
I notice this when reviewing PR’s all the time. Most people don’t even follow simple stuff like the naming conventions of the code base they’re in and just do it ‘their way’. I’m sorry but I’m not merging a PR like that. (Yes, I know that there are tools that can enforce this, it’s just an example.)
If I can go through a projects code base and tell you which developers on the team wrote each section of the entire app then you’ve utterly failed as a dev team. You can call that conformity or whatever but that’s what makes code easy to read and maintain. I don’t want to have to read or worse refactor the same problem from 4 different implementations because each dev on the team decided they wanted to do it their way.
I notice this when reviewing PR’s all the time. Most people don’t even follow simple stuff like the naming conventions of the code base they’re in and just do it ‘their way’. I’m sorry but I’m not merging a PR like that. (Yes, I know that there are tools that can enforce this, it’s just an example.)