>No, it's about representation of information in a system, as your own Wikipedia link states right up at the top of the second paragraph.
That's a little too broad to be useful, IMO. I learned the DRY principle before that book came out, and it was strictly about not repeating yourself in code. You can apply it to other things, but it was originally code. Normal form is a good example of applying DRY to RDBMS systems/schemas. "Single source of truth," is a good example of applying DRY to separate database systems. None of those were considered part of the DRY principle when I was starting out.
>They apply it quite broadly to include "database schemas, test plans, the build system, even documentation".
The article even hints those particular authors expanded on it beyond its original intent. They certainly didn't invent it.
That's a little too broad to be useful, IMO. I learned the DRY principle before that book came out, and it was strictly about not repeating yourself in code. You can apply it to other things, but it was originally code. Normal form is a good example of applying DRY to RDBMS systems/schemas. "Single source of truth," is a good example of applying DRY to separate database systems. None of those were considered part of the DRY principle when I was starting out.
>They apply it quite broadly to include "database schemas, test plans, the build system, even documentation".
The article even hints those particular authors expanded on it beyond its original intent. They certainly didn't invent it.