# The DRY Principle

DevFeed: [The DRY Principle](<https://devfeed.tech/articles/the-dry-principle-40683.md>)

Original publisher: [Read original article](<https://radek.io/posts/dry-principle/>)

Published: 2012-01-19T00:00:00Z

Content type: article

Language: en

Sources: [Radek Pazdera](<https://devfeed.tech/sources/radek-pazdera.md>)

Topics: [Software Engineering](<https://devfeed.tech/topics/software-engineering.md>), [Architecture & Design](<https://devfeed.tech/topics/architecture-design.md>), [Database](<https://devfeed.tech/topics/database.md>)

Tags: [database](<https://devfeed.tech/tags/database.md>), [development](<https://devfeed.tech/tags/development.md>), [software](<https://devfeed.tech/tags/software.md>), [software-design](<https://devfeed.tech/tags/software-design.md>), [software-development](<https://devfeed.tech/tags/software-development.md>)

## AI overview

The article explains the DRY principle: every piece of knowledge should have a single authoritative representation within a software system. It uses database schema definitions as an example, showing how duplicating them across design documents, scripts, and code creates synchronization work and can leave the system inaccurate after later changes.

## Source excerpt

I build software products and write on the Internet.