Don’t Repeat Yourself across integration-test code and production code?
I totally believe in not repeating yourself in production code. I’ve accepted the idea that you shouldn’t repeat yourself within test code. But what happens when you have production services that would simplify test code?
Avoid code repetition in CRUD operations
I’m developing a PHP application and I find myself doing basically the same code for, say, creating an object based on a form filled by the user.
Avoid code repetition in CRUD operations
I’m developing a PHP application and I find myself doing basically the same code for, say, creating an object based on a form filled by the user.
Avoid code repetition in CRUD operations
I’m developing a PHP application and I find myself doing basically the same code for, say, creating an object based on a form filled by the user.
DRY code, DRY tests?
At some point I had to create some class “Class1” and that class needs a method “method”. So I have the following:
DRY code, DRY tests?
At some point I had to create some class “Class1” and that class needs a method “method”. So I have the following:
DRY code, DRY tests?
At some point I had to create some class “Class1” and that class needs a method “method”. So I have the following:
How do you wrestle the DRY principle with configs?
For instance, lets say we have an nginx config pointing at foo1, foo2, and foo3, as well as a haproxy config pointing at foo1, foo2, and foo3, and finally, a deployment tool pointing at the same respective servers.
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]; […]
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]; […]