Skip to main content
6 events
when toggle format what by license comment
Nov 1, 2017 at 3:05 comment added G.T.D. @user949300 I will add a more comprehensive example that correctly shows what I am thinking as everyone has misinterpreted my current example (to no fault of their own, I just did not think to provide a fully detailed example as I did not think it was needed). I will edit in a new one tomorrow that much more detailed and comprehensive, this should explain my position MUCH better.
Nov 1, 2017 at 3:01 comment added G.T.D. @user949300 Technically yes but only to demonstrate my concern with this being a good path. In reality my example would not actually violate DRY as I would not be duplicating effort (my domain model would be for a completely different reason than my data access model). The core of the issue with the current answers is that my example code is VERY pseudo code (i.e. requires a lot of reading beyond the example code) and not comprehensive enough to actually show my thinking. I planned on editing in a better example shortly after Robert posted his answer, but I just have not gotten around to it.
Oct 31, 2017 at 18:30 comment added user949300 @B1313 But your boilerplate code violates DRY and LEAN. The nice thing about software design principles is that, like "standards", there are so many of them. :-) Which is what Robert is getting at in his answer and comment.
Oct 23, 2017 at 3:21 comment added Robert Harvey @B1313: The best practice is the one that most effectively meets your specific software requirements. Ask yourself: what benefits do I get by duplicating functionality that I already have in another class?
Oct 22, 2017 at 17:23 comment added G.T.D. Isn't glueing the domain model to the ORM bad practice for separation of concern, single responsibility principle, and encapsulation?
Oct 22, 2017 at 6:18 history answered Robert Harvey CC BY-SA 3.0