The DRY principle is stated as "Every piece of knowledge must have a single, unambiguous, authoritative representation within a system".
[1] They apply it quite broadly to include database schemas, test plans, the build system, even documentation.
WET solutions are common in multi-tiered architectures where a developer may be tasked with, for example, adding a comment field on a form in a web application.
The text string "comment" might be repeated in the label, the HTML tag, in a read function name, a private variable, database DDL, queries, and so on.
AHA programming assumes that both WET and DRY solutions inevitably create software that is rigid and difficult to maintain.