... Yes, sorry, I wasn't clear enough. My response was to this single piece ... Where ICustomerRepository comes from the domain layer and Repository<Customer>...
... Yeah definitely, I should have said "if you want to keep the ubiquity of language then you have two choices"....
9079
Rafael Ponte
rponte@...
Dec 1, 2008 12:20 pm
I really think only interesting a generic repository to facilitate the creation of CRUDs, anything beyond this is prejudicial for domain. Because it's not...
... Most of the domain experts or users I interact with can understand the Role/Player pattern. May be I'm lucky. They understand what a Company is and...
You assume users want to be problem solvers - and most don't - they want a tool to get their job done. Excel and Word are "problem solving" pieces of software...
Another option instead of a generic interface/class is a non-generic class with generic members: IRepository { T Find<T>(Guid id); void Update(T entity); } ...
This is exactly how we construct our repositories too. Symon. ... -- Symon Rottem http://blog.symbiotic-development.com This is exactly how we construct our...
Cannot delete why? Business rule or database restriction? Surely the method throwing is a better idea than repositories not sharing common interfaces, and...
IRepository<T> in C# fulfills 90% of repository requirements Casey ... IRepository<T> in C# fulfills 90% of repository requirements Casey On 30 Nov 2008, at...
... , Temporal Object <http://martinfowler.com/eaaDev/TemporalObject.html>, and Role and Player <http://c2.com/cgi/wiki?RoleAndPlayer>, but my supposed "domain...
... As Randy and yourself pointed out, this person was not really a domain expert, but the implication still seemed to be there that a domain expert should...
... Are you saying that you would allow the language you use in discussions with the domain expert to be very different to the language you use in your code?...
Wouldn't that be the other way around... Technical language shouldn't enter the UL? My reading was that the UL is driven by the domain experts. Casey Charlton ...
... Perhaps, in that language, but if they recognize the need for such patterns and their implications when describing the domain, it's all the same. You ...
... No. What I mean is that the ubiquitous language is a pidgin. There are terms on either side that aren't relevant to the shared discussion and sharing them...
... shouldn't ... To me its about more than that though. One section I find useful is "One team, one language" but the chapter "Model-Driven Design" is also ...
... with ... patterns ... same. You ... Patterns", ... for an ... always ... if they ... patterns, ... communication ... The topic is "Ubiquity of Language"...
I'm not sure where to drop into this conversation, so I'll just stick my $.02 in here. What I think is going on is a bit of inflexibility. Some domain experts...
... Are you saying that you would allow the language you use in discussions with the domain expert to be very different to the language you use in your code? ...
... Snap but are you just meaning that C# as a language naturally leads you away from a UL centric approach, or were you just meaning that the code is not...
... Right: pidgin == "jargon consensus" Take your pick. There are always going to be concepts in the code that aren't part of the language you share with the...
... Sure, having said that patterns like accountability and party-role change key parts of the model so some level of understanding is useful. Otherwise you...
... Sorry, I didn't mean to imply that at all -- I'm just saying that if's possible for the domain and the language to reflect the needs of the business...
... I'd say that you are sacrificing the UL, its a trade-off but you are allowing the model the development team use (design model) to vary separately from the...
... Yeah I agree. So would you avoid using the patterns terminology in the code too? Also You made a good point on temporal patterns earlier, and they are ...
... I don't believe it is all or nothing. When we use UML, or any other pseudo-language, we leave out details that we consider immaterial to the discussion. We...
... This is where I handwave and say "it depends". ;) Like all methods, I'm inclined to believe that teams may need to adapt DDD to their specific situation,...
... I agree its not all or nothing, I didn't say it was (was careful not to say that and I don't think anyone has said that, so we are all in total agreement...
