> I think there's a big cultural challenge with adopting duplication. It goes against most people's career growth objectives. My experience is the complete opp

> I think there's a big cultural challenge with adopting duplication. It goes against most people's career growth objectives. My experience is the complete opposite :D. What I've noticed is that the people who 'deliver' quickly (without much regard for what might be called code quality) and fulfill business requirements without much questioning are perceived as more valuable. > I've found that my work is often far more limited by the domain/business logic than any sort of programming logic. I broadly agree with this statement. However, just like a good carpenter knows how to properly build a bookcase, a table, a roof etc. a good developer should understand the programming logic and know how to apply it. Business requirements need to be fulfilled, but it's up to us to decide how to do that. More so, I think it's up to us to push back when we feel business requirements don't make sense from a technical point of view, or even from a business point of view.