DRY
The DRY principle states that “every piece of knowledge or logic must have a single, unambiguous representation within a system.” In practice, this means:
- Avoid duplicating code across your codebase
- Abstract common functionality into reusable components (functions, classes, modules)
- When you find yourself writing similar code more than once, it's time to refactor
Benefits of DRY:
- Reduces maintenance burden (change once, update everywhere)
- Decreases chances for bugs (fewer places to fix issues)
- Makes code more readable and maintainable