login/register

Snip!t from collection of Alan Dix

see all channels for Alan Dix

Snip
summary

Don't Repeat Yourself (DRY, also known as Single Point o... process philosophy aimed at reducing duplication, partic... computing. The philosophy emphasizes that information sh... duplicated, because duplication increases the difficulty... decrease cl

Don't repeat yourself - Wikipedia, the free encyclopedia
http://en.wikipedia.org/wiki/Don't_repeat_yourself

Categories

/Channels/techie/debugging

[ go to category ]

For Snip

loading snip actions ...

For Page

loading url actions ...

Don't Repeat Yourself (DRY, also known as Single Point of Truth) is a process philosophy aimed at reducing duplication, particularly in computing. The philosophy emphasizes that information should not be duplicated, because duplication increases the difficulty of change, may decrease clarity, and leads to opportunities for inconsistency. DRY is a core principle of Andy Hunt and Dave Thomas's 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 change other logically-unrelated elements. Additionally, elements that are logically related all change predictably and uniformly, and are thus kept in sync.

HTML

<b>Don't Repeat Yourself</b> (DRY, also known as Single Point of Truth) is a process philosophy aimed at reducing duplication, particularly in <a href="/wiki/Computing" title="Computing">computing</a>. The philosophy emphasizes that <a href="/wiki/Information" title="Information">information</a> should not be duplicated, because duplication increases the difficulty of change, may decrease clarity, and leads to opportunities for <a href="/wiki/Inconsistency" class="mw-redirect" title="Inconsistency">inconsistency</a>. DRY is a core principle of <a href="/wiki/Andy_Hunt_%28author%29" title="Andy Hunt (author)">Andy Hunt</a> and <a href="/wiki/Dave_Thomas_%28author%29" class="mw-redirect" title="Dave Thomas (author)">Dave Thomas</a>'s book <i><a href="/wiki/The_Pragmatic_Programmer" title="The Pragmatic Programmer">The Pragmatic Programmer</a></i>. They apply it quite broadly to include "<a href="/wiki/Database" title="Database">database</a> schemas, <a href="/wiki/Test_plan" title="Test plan">test plans</a>, the <a href="/wiki/Software_build" title="Software build">build</a> system, even <a href="/wiki/Software_documentation" title="Software documentation">documentation</a>."<sup id="cite_ref-HuntThomasBroadInfo_0-0" class="reference"><a href="#cite_note-HuntThomasBroadInfo-0" title="">[1]</a></sup> When the DRY principle is applied successfully, a modification of any single element of a system does not change other logically-unrelated elements. Additionally, elements that are logically related all change predictably and uniformly, and are thus kept in <a href="/wiki/Synchronization" title="Synchronization">sync</a>.