SOLID
This principle was given by Robert C. Martin and Michael Feathers to encourage us to create more maintainable, understandable, and...
For further actions, you may consider blocking this person and/or reporting abuse
About the DRY principle, I think you put it in a too simplistic way. Actually DRY is not about code repetition, the principle rather refers on information, and knowledge in the system.
When you find duplicated code in your system, you should check if all the different part with that code are actually working on the same piece of information.
In that case you can try to find an abstraction, and you can refactor your code base in a way that this logic is placed in one place and just used where it is needed, getting rid of the duplicated code.
If the code is the same, but is working on differen business entities, you may better to leave it duplicated, as it may will diverge in the future.
If you change it and then you have to implement a new requirement that change the behaviour in one place, but not in the other, then you are forced to introduce complexity to handle the feature.
Thanks for your feedbacks!
Great share and welcome to dev.
Thank you so much!!!
Nicely explained. The examples make it clear to understand👍🏻
Thank you so much!!!
Useful! Thanks!
You're welcome.
Excellent. You're really good.
You are too kind.
Amazing post. Keep it up buddy!
Thank you so much!!!
I have learned so much. Thanks.
Amazing 💝