DRY principle
E97054
The DRY (Don't Repeat Yourself) principle is a software development guideline that emphasizes reducing repetition by centralizing logic and data to improve maintainability and reduce errors.
All labels observed (2)
| Label | Occurrences |
|---|---|
| DRY principle canonical | 3 |
| Don’t Repeat Yourself | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T816282 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
Target entity: DRY principle Context triple: [Django, designGoal, DRY principle]
-
A.
Occam's razor
Occam's razor is a philosophical and scientific principle that advises preferring the simplest explanation that adequately accounts for all observed facts.
-
B.
Clean Code: A Handbook of Agile Software Craftsmanship
Clean Code: A Handbook of Agile Software Craftsmanship is a highly influential software engineering book by Robert C. Martin that teaches principles and practices for writing readable, maintainable, and high-quality code.
-
C.
Refactoring: Improving the Design of Existing Code
"Refactoring: Improving the Design of Existing Code" is a seminal software engineering book by Martin Fowler that systematically defines refactoring techniques to improve code structure while preserving behavior.
-
D.
The Pragmatic Programmer
The Pragmatic Programmer is a highly influential software development book that offers practical advice, best practices, and philosophical guidance for writing maintainable, high-quality code and growing as a professional programmer.
-
E.
Working Effectively with Legacy Code
Working Effectively with Legacy Code is a widely respected software engineering book by Michael Feathers that teaches practical techniques for understanding, testing, and safely modifying existing codebases.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Target entity: DRY principle Target entity description: The DRY (Don't Repeat Yourself) principle is a software development guideline that emphasizes reducing repetition by centralizing logic and data to improve maintainability and reduce errors.
-
A.
Occam's razor
Occam's razor is a philosophical and scientific principle that advises preferring the simplest explanation that adequately accounts for all observed facts.
-
B.
Clean Code: A Handbook of Agile Software Craftsmanship
Clean Code: A Handbook of Agile Software Craftsmanship is a highly influential software engineering book by Robert C. Martin that teaches principles and practices for writing readable, maintainable, and high-quality code.
-
C.
Refactoring: Improving the Design of Existing Code
"Refactoring: Improving the Design of Existing Code" is a seminal software engineering book by Martin Fowler that systematically defines refactoring techniques to improve code structure while preserving behavior.
-
D.
The Pragmatic Programmer
The Pragmatic Programmer is a highly influential software development book that offers practical advice, best practices, and philosophical guidance for writing maintainable, high-quality code and growing as a professional programmer.
-
E.
Working Effectively with Legacy Code
Working Effectively with Legacy Code is a widely respected software engineering book by Michael Feathers that teaches practical techniques for understanding, testing, and safely modifying existing codebases.
- F. None of above. chosen
Statements (50)
| Predicate | Object |
|---|---|
| instanceOf |
software development principle
ⓘ
software engineering guideline ⓘ |
| abbreviation | DRY ⓘ |
| aimsTo |
improve consistency
ⓘ
improve maintainability ⓘ reduce errors ⓘ simplify changes ⓘ |
| appliesTo |
build scripts
ⓘ
configuration management ⓘ database schemas ⓘ documentation ⓘ source code ⓘ test cases ⓘ |
| canBeViolatedBy |
copy-paste programming
ⓘ
duplicated business rules ⓘ duplicated configuration values ⓘ |
| canLeadTo | over-abstraction if misapplied ⓘ |
| contrastedWith |
WET code
ⓘ
shotgun surgery ⓘ |
| encourages |
abstraction
ⓘ
centralizing business logic ⓘ centralizing configuration ⓘ centralizing validation rules ⓘ modular design ⓘ reuse of code ⓘ single source of truth ⓘ |
| focusesOn |
reducing duplication of code
ⓘ
reducing duplication of data ⓘ reducing duplication of logic ⓘ |
| fullName |
DRY principle
self-linksurface differs
ⓘ
surface form:
Don’t Repeat Yourself
|
| helpsWith |
avoiding divergence of duplicated logic
ⓘ
improving readability ⓘ improving testability ⓘ reducing bug surface area ⓘ reducing maintenance cost ⓘ |
| isMentionedIn | software engineering literature ⓘ |
| isUsedIn |
API design
ⓘ
functional programming ⓘ object-oriented programming ⓘ procedural programming ⓘ web application development ⓘ |
| originatedIn | software engineering community ⓘ |
| relatedTo |
KISS principle
ⓘ
Single Responsibility Principle ⓘ YAGNI principle ⓘ code reuse ⓘ refactoring ⓘ |
| supports |
clean architecture
ⓘ
domain-driven design ⓘ layered architecture ⓘ |
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Subject: DRY principle Description of subject: The DRY (Don't Repeat Yourself) principle is a software development guideline that emphasizes reducing repetition by centralizing logic and data to improve maintainability and reduce errors.
Referenced by (4)
Full triples — surface form annotated when it differs from this entity's canonical label.