Coding for 20 years | Working for startups for 10 years | Team leader and mentor | More information about me: https://thevaluable.dev/page/about/
Twitter: @Cneude_Matthieu
The DRY principle is not about code duplication, but knowledge duplication. It's not the same thing at all. From the Pragmatic Programmer, the book which coined the term, DRY is defined as:
Every piece of knowledge must have a single, unambiguous, authoritative representation within a system.
Other than that, all these principles are nice and we should definitely know them, but always keep in mind that it depends on the context you're in. Don't apply them blindly, think before if it's wise to apply them.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
The DRY principle is not about code duplication, but knowledge duplication. It's not the same thing at all. From the Pragmatic Programmer, the book which coined the term, DRY is defined as:
This makes a big difference I explain here.
Other than that, all these principles are nice and we should definitely know them, but always keep in mind that it depends on the context you're in. Don't apply them blindly, think before if it's wise to apply them.