Principles and Architecture / Rules of thumb
DRY
Original notes by SunDiaL · View English source
Don't Repeat Yourself
Every piece of knowledge must have a single, unambiguous, authoritative representation within a system
- If it's code, extract it into classes/methods/fields instead of copy-pasting
- If it's documentation, write it only once
- If it's code documentation, ideally have the code generate the documentation itself
If there's two things saying the same thing they will eventually get out of sync.