Tag: dry

Found 71 results for 'dry'.

1) c++ - Reducing code duplication between operator= and the copy constructor
2) design-patterns - Modify Command object inside decorator of CommandHandler(CQRS) or any other practice for avoiding duplication
3) coding-standards - Validation of the input parameter in caller: code duplication?
4) object-oriented - Is 'Keep it looks similar to sample code' a valid reason to prefer WET over DRY principle?
5) c# - Unit testing and reusing extracted class
6) php - DRY with Dynamic SQL vs. prepared statements
7) php - Avoid code repetition in CRUD operations
8) project-management - Best practices for sharing tiny snippets of code across projects
9) design - What should I consider when the DRY and KISS principles are incompatible?
10) design - Reduce DRY for different classes which have the same data model
11) design - DRY principle often makes my code more complicated and/or more difficult to understand
12) tdd - Refactoring: reducing duplication without creating flags
13) design - Is it possible to apply DRY without increasing coupling?
14) php - DRY principles vs local-only variable scope in functions (PHP motivated question)
15) testing - Is coding and unit testing violating the DRY principle
16) version-control - How to avoid code duplication across unrelated projects
17) c# - Is it poor practice to have a class implement an abstract class without adding any new fields/members/functionality?
18) java - Does decoupling trump DRY in REST?
19) c - How to handle repetitive mallocs/frees in a DRY way in C
20) design-patterns - Modify Command object inside decorator of CommandHandler(CQRS) or any other practice for avoiding duplication
21) design - Does my code violate DRY principle?
22) design-patterns - How to make updates to data and return list of updates without breaking Command query separation or DRY?
23) design-patterns - Call class method only if condition is met
24) jquery - WebForms, JQuery and the DRY principle
25) c++ - Const C++ DRY Strategies
26) database - How to DRY with calls to a database to execute?
27) inheritance - Is "composition over inheritance" violating "dry principle"?
28) angularjs - Tab management code in single-page applications acceptable violations of the DRY principle?
29) design-patterns - Is duplicating files to avoid programming branching a good or anti pattern?
30) testing - Doesn't single-assert unit testing break the DRY principle?
31) comments - Approaches for comment duplication
32) refactoring - DRY code, DRY tests?
33) architecture - How to avoid code duplication in two similar projects?
34) design - Don't Repeat Yourself Vs Single Point Of Failure in authentication
35) .net - How do you keep SOA DRY?
36) terminology - Violation of the DRY Principle
37) unit-testing - How to write DRY Unit Tests when order of method calls matters
38) mvc - What did the reviewer refer to in this code review?
39) code-quality - Why is DRY important?
40) design - Redundant function to clarify purpose?
41) design-patterns - Should I only load in the code I need if there's no performance impact for loading all of it
42) javascript - I keep bouncing from "god function" to "tiny SRP functions" how do I break this cycle?
43) java - DRY principle vs decoupling (business from GUI)
44) business - Forking an application for an "enterprise" customer
45) design - Managing client-side and server-side validations in one place
46) tdd - Behat/Mink: best practice for testing strings in a web application's GUI
47) coding-style - Is copy and paste the head of for-loop (e.g.:for(let i=0;i<something.length;i++)) violating DRY principle?
48) c# - How to implement DRY principle when using 'using' keyword?
49) c# - DRY unrelated, but nearly identical, code
50) programming-practices - Is there a drawback in defining multiple small DRY classes, instead of bigger more repetitive classes?