The importance of duplicate code removal [duplicate]
This question already has answers here: Why is DRY important? (15 answers) Closed 9 years ago. I tried to explain to a coworker the gravity of having duplicate code in a project, on this piece of code: + (void)createIapInParse:(SKPaymentTransaction *)transaction { Reachability *reach = [Reachability reachabilityWithHostname:@”www.facebook.com”]; if ([Social getFBUser]) { NSString *iapId = [Util getBundleNameFromIdentifier:transaction.payment.productIdentifier]; […]
Refactoring: reducing duplication without creating flags
I don’t know how to refactor a piece of code that differs from other in the number of conditions checked on an if clause. Let me show you a real world example I’m facing right now.
Is it acceptable to refactor a collaborator’s code?
When working with other people in a project, is it acceptable to refactor some of their code?
Separation of logic from presentation results in repetition of code
Here’s what I’ve been thinking.
How to sell DRY architecture [duplicate]
This question already has answers here: How to convince my boss that quality is a good thing to have in code? [duplicate] (25 answers) Closed 9 years ago. I’m sure most are familiar with the phrase DRY in the software world – Don’t Repeat Yourself. This is a fundamental principle of good software development. Here […]
2 methods that are 75% the same? [closed]
Closed 9 years ago.
2 methods that are 75% the same? [closed]
Closed 9 years ago.
2 methods that are 75% the same? [closed]
Closed 9 years ago.
2 methods that are 75% the same? [closed]
Closed 9 years ago.
2 methods that are 75% the same? [closed]
Closed 9 years ago.