u/lousybytein r/dotnet • Recommends
On “How to avoid duplicate validations on same entity between two handlers”
DRY is a principle, not a hard rule, it all depends on your use case.
I recommend watching Derek's video: [video
0:00 / 0:00
#dryprinciple#coupling#verticalslicearchitecture
DRY principle is why your codebase sucks?
CodeOpinion
101K subscribers • 2 videos on Hallway
- Recommended by 1 person: 1 in engineering communities.
- Presented by Derek Comartin
- An opinion. It argues one side of a question engineers disagree on.
Intermediate. Assumes working knowledge.
12K views2 years ago1 recommendation
Software designDesign patternsSimplicity and complexitySoftware architecture
Derek Comartin explains how dogmatic application of the DRY principle can lead to tight coupling and complex, hard-to-change codebases.
DRY Principle is seemingly advocated for or against. In reality, it's not good or bad so as long as you understand why you're applying it and for what purpose. Misunderstanding DRY is why your system can turn into a hard to change rats nest. 🔗 EventStoreDB eventsto.re/codeopinion 🔔 Subscribe: youtube.com/channel/UC3RKA4vunFAfrfxiJhPEplw?sub_confirmatio… 💥 Join this channel to get access to a private Discord Server and any source code in my videos. 🔥 Join via Patreon patreon.com/codeopinion ✔️ Join via YouTube youtube.com/channel/UC3RKA4vunFAfrfxiJhPEplw/join 📝 Blog: codeopinion.com 👋 Twitter: twitter.com/codeopinion ✨ LinkedIn: linkedin.com/in/dcomartin/ 📧 Weekly Updates: mailchi.mp/63c7a0b3ff38/codeopinion DRY Coupling Entities VSAWhy it's here
1 person recommends thisWhat people say. Recommended as a great explanation of when to apply the DRY principle and when duplication is preferred to avoid coupling.