Refactoring
-
We have a developer on our team that almost always feels the need to refactor the code. The effort is appreciated and it's often better than before. but... - It's often not really necessary, the code was working as intended and not bad or untidy. - Premature optimization in some cases. - The code needs to go through review and testing again. - It's largely based on one person's likes and dislikes for naming and structure which may not always be easier for others to understand. They tend to break it into very small chunks / files, and it can be difficult to get the bigger picture and follow the flow. It becomes a bit disconnected in some cases. - It can be discouraging sometimes, whatever I code is just going to get refactored anyway. Maybe I shouldn't be too personally attached to my code, but I think most developers are. I don't want to discourage this person and squash their enthusiasm, but it might need to be addressed. I also have a different philosophy / style due to past projects where I had limited time and often had to just get things working, while still trying to keep things tidy. Any advice on dealing with this situation?