Content Lexicon.

DRY

In one line

“Don’t repeat yourself”: keep one reliable source of truth instead of many drifting copies.

DRY stands for “don’t repeat yourself”. In software, it means every piece of knowledge should have a single, authoritative representation, so a change is made in one place. In content, the same principle applies to definitions, policy wording, product copy, service descriptions, statistics, instructions and guidance. If the same fact or passage exists in five places, those five places eventually start disagreeing with one another.

DRY doesn’t mean everything should be written only once, in identical words. Sometimes repetition is useful for readers. What needs one authoritative home is the underlying fact, decision or source, even if it’s expressed in different ways for different contexts.

Why it matters for content

DRY reduces drift, contradiction and needless maintenance. It helps teams update information once rather than hunting for every copy, and it makes content easier to govern because there’s less ambiguity about which version is the right one. It’s especially valuable where the same information appears across channels, teams or formats.

The facts and assets that change over time need it most: prices, statistics, policy wording, service descriptions, eligibility criteria, boilerplate copy, brand guidance and recurring explanations. They’re also the things organisations copy and paste most freely.

How AI changes the picture

Generating a new copy of something now costs almost nothing, while maintaining it costs what it always did. Ask an assistant for a fresh eligibility summary for a campaign page and you get a near-duplicate, worded slightly differently, that nobody will remember to update when the criteria change. Retrieval adds a second problem: a chatbot that finds three versions of the same policy may quote the oldest, or blend them into a fourth that appears nowhere.

Used well, AI supports DRY: it can rework one structured source into a summary, an FAQ answer or a social post, each drawn from the same original. That depends on there being a reliable original to draw from.

Questions people ask

Does DRY mean never repeating anything?

No. Readers often need reinforcement, summaries or context-specific wording. DRY is about not maintaining several competing sources for the same underlying information.

Is DRY only for technical teams?

Not at all. Content teams deal with repeated facts, definitions and guidance all the time. In some organisations they deal with it more than developers do.

Can DRY go too far?

Yes. If everything is forced into one abstract source when readers need tailored wording, the result can become harder to use. DRY should reduce duplication without flattening context.

Is DRY the same as a single source of truth?

They’re closely related. DRY is the principle of reducing unnecessary duplication; a single source of truth is often the practical way of doing it.

Learn more

  • The Pragmatic Programmer on DRY – the authorised “The Evils of Duplication” excerpt from The Pragmatic Programmer, explaining duplication of knowledge rather than only repeated code.
  • Avoiding Repetition – Martin Fowler’s IEEE Software essay on why repeated knowledge creates maintenance trouble.
  • The Wrong Abstraction – Sandi Metz’s counterpoint that “duplication is far cheaper than the wrong abstraction”, and how forcing shared code onto cases that have drifted apart makes it harder to change.

Type a term, or a word from its definition.⌘K opens this from any page.