CSC/ECE 517 Fall 2009/wiki3 4 ashi4: Difference between revisions
No edit summary |
|||
| Line 4: | Line 4: | ||
== Introduction == | == Introduction == | ||
<i>Donot Repeat Yourself (DRY)</i> also known as <i>Duplication Is Evil (DIE)</i> is one of the most fundamental principles of programming, or rather we can say that it is the most important principle of good programming. This principle was formulated by Andrew Hunt and David Thomas in their book [[References#1 | The Pragmatic Programmer]]. The principle states that "Every piece of knowledge must have a single, unambiguous, authoritative representation within a system.". This principle has been broadly accepted and acknowledged by the developers across the globe. It is considered to be one of the best coding practices to build an efficient and flexible code which is not only easy to understand but easy to maintain too. A parallel concept to DRY is <b>Orthogonality</b> which is making the components of the system as functionally independent as possible. It is well understood and an accepted fact that the DRY and the Orthogonality principle together lead to a very well structured code as discussed [http://www.artima.com/intv/dry3.html | here]. The purpose of this document is to emphasize on the fact that the DRY principle is not only applicable to the code but to the data as well. | |||
== Some Basic Terminologies == | == Some Basic Terminologies == | ||
Revision as of 23:35, 18 November 2009
DRY Principle for Data
Introduction
Donot Repeat Yourself (DRY) also known as Duplication Is Evil (DIE) is one of the most fundamental principles of programming, or rather we can say that it is the most important principle of good programming. This principle was formulated by Andrew Hunt and David Thomas in their book The Pragmatic Programmer. The principle states that "Every piece of knowledge must have a single, unambiguous, authoritative representation within a system.". This principle has been broadly accepted and acknowledged by the developers across the globe. It is considered to be one of the best coding practices to build an efficient and flexible code which is not only easy to understand but easy to maintain too. A parallel concept to DRY is Orthogonality which is making the components of the system as functionally independent as possible. It is well understood and an accepted fact that the DRY and the Orthogonality principle together lead to a very well structured code as discussed | here. The purpose of this document is to emphasize on the fact that the DRY principle is not only applicable to the code but to the data as well.