Instantly share code, notes, and snippets.
updated list moved to https://grin.io/coding-maxims
DRY is a dangerous mantra when applied without thinking... If your crossing architectural boundaries, and you think that it's "DRY" to share your dto from one boundary to another all the way down to your persistence layer because, if you don't, your repeating yourself, then your going to be asking for a world of pain in terms of coupling between layers ... DRY within a bounded context / specific scope is the only way to apply this principal...
The rest of your principles are well written and unfortunately I don't see enough like them in other places.
Sorry, something went wrong.
Great Maxims Lyoshenka
I love DRY as much as the next guy but when you are moving fast, I think sometimes it’s okay to save things to factor out later. What do you think about the Sandi Metz saying “duplication is far cheaper than the wrong abstraction”.?
Thanks for the Maxims!.
@rchasman he's probably right. As the last maxim says, "first you don't know the rules, then you learn the rules, then you break the rules".