addisoncave
Familiar Face
Hey Guys, Please tell me what is DRY code? I've created a Project in PHP and a reviewer said me to use DRY codes.. and Now I don't know what are DRY codes? can anyone elaborate what are DRY codes?
What are DRY Codes?
- Thread starter addisoncave
- Start date
2arjupraja
Acquaintance
Whether in code, design, prerequisites reports, or client documentation, duplication of information - not simply message - is the genuine guilty party. Along these lines: The DRY (Don't Repeat Yourself) Principle expresses: Every bit of learning must have a solitary, unambiguous, definitive representation inside a framework.
Nancennedy
New Arrival
The DRY rule is expressed as "Each bit of learning must have a solitary, unambiguous, legitimate representation inside a framework". The standard has been defined by Andy Hunt and Dave Thomas in their book The Pragmatic Programmer. They apply it extensively to incorporate "database mappings, test arranges, the manufacture framework, even documentation."[1] When the DRY rule is connected effectively, an adjustment of any single component of a framework does not require a change in other legitimately random components
Piki Sharika Varki
Acquaintance
DRY Codes: In software engineering, don't repeat yourself is a principle of software development, aimed at reducing repetition of information of all kinds, especially useful in multi-tier architectures, Thanks .
In software engineering, don't repeat yourself (DRY) is a principle of software development, aimed at reducing repetition of information of all kinds, especially useful in multi-tier architectures.
The DRY principle is stated as "Every piece of knowledge must have a single, unambiguous, authoritative representation within a system". The principle has been formulated by Andy Hunt and Dave Thomas in their book The Pragmatic Programmer. They apply it quite broadly to include "database schemas, test plans, the build system, even documentation."[1] When the DRY principle is applied successfully, a modification of any single element of a system does not require a change in other logically unrelated elements. Additionally, elements that are logically related all change predictably and uniformly, and are thus kept in sync. Besides using methods and subroutines in their code, Thomas and Hunt rely on code generators, automatic build systems, and scripting languages to observe the DRY principle across layers.
The DRY principle is stated as "Every piece of knowledge must have a single, unambiguous, authoritative representation within a system". The principle has been formulated by Andy Hunt and Dave Thomas in their book The Pragmatic Programmer. They apply it quite broadly to include "database schemas, test plans, the build system, even documentation."[1] When the DRY principle is applied successfully, a modification of any single element of a system does not require a change in other logically unrelated elements. Additionally, elements that are logically related all change predictably and uniformly, and are thus kept in sync. Besides using methods and subroutines in their code, Thomas and Hunt rely on code generators, automatic build systems, and scripting languages to observe the DRY principle across layers.
david hong
Familiar Face
DRY is a basic tenet of the program was designed to minimize the purpose of writing the code repeated several times only to perform the same job in the application.
rohitvpp11
New Arrival
In software engineering, don't repeat yourself (DRY) is a principle of software development, aimed at reducing repetition of information of all kinds, especially useful in multi-tier architectures. ... The principle has been formulated by Andy Hunt and Dave Thomas in their book The Pragmatic Programmer.
Affiliates
