4 ms·
Let me add to this... Any experienced developer is going to dislike her new team's code. It's just the way developers are. They like the code to match the way
by smt88 6y ago
Let me add to this...
Any experienced developer is going to dislike her new team's code. It's just the way developers are. They like the code to match the way they think or what they're used to. New code bases are always counter-intuitive at first, and it feels like that wastes your time.
That means every new, experienced hire is going to want to refactor. It does not mean they should refactor or that anything is actually urgently wrong with the code.
I've had people who refactored, broke their build, couldn't fix, and ended up scrapping the branch entirely. It was a complete waste of time.
- sevensor 6y agoI don't see that as a waste of time at all. The programmer learned a lot and didn't damage the codebase, assuming the changes went unmerged. This sounds like a pretty good way to come to grips with the problem domain.
- detaro 6y agoThat's true, not how I took the question but it can totally be a valid strategy to help understanding of the code base.
- WolfOliver 6y agoI agree to this observation. Especially in teams with hight fluctuation they spend most of the time refactoring their code in cycles to fit some personal taste.