Friday, December 27, 2002

Martin Folwer With Some Insightful Comments Regarding the limitations that might be encountered when using the Object / Summary Pattern: "It's important to stress that in this scheme you can't support editable tables, at least not without some tricky or duplicate coding. Obviously this isn't an issue in many places, but for some it could be." "You'd need to say something about derived information. Either you need objects to update the data set, putting the logic in a third place (which may lead to structuring difficulties for larger apps), or duplication (ugh)." "If the domain model is quite rich and departs from the database schema this may make things awkward because you don't have the (assumingly better) domain model to help you with your queries." "Those are just thoughts off the top of my head. Just because I've mentioned limitations doesn't mean I don't think it's a good technique - I'm just trying to think of both sides of the coin." Great insight from the master if you are planning on following using the same type of pattern in your application(s). 10:56:27 PM    comment []

More Books I ordered the Mythical Man Month today. I am trying to get through some of those classics that I haven't gotten around to reading yet. Definately looking forward to it. Update on the rest: Fowler's book is great, it does for enterprise patterns what Gang of Four (Design Patterns) did for generic object based patterns (also a must read, if for some reason, you haven't already). Box's book is really interesting if you want to know some of those wierd CLR internals that never really get explained (definately a better choice for learning about the CLR than Inside Microsoft .NET IL Assembler). Ingo's book is good too if you are going to be doing remoting. Lots of in-depth info that you would be hard pressed to find in any other single source. 2:37:43 PM    comment []