tag:blogger.com,1999:blog-7442262522977329981.post2282431734275832222..comments2012-01-18T09:34:46.851-06:00Comments on Turbulent Intellect: You'll POCO Your Eye Out!Chris Ammermanhttps://profiles.google.com/118440544456036580001noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-7442262522977329981.post-61614340697315918192012-01-18T09:34:46.851-06:002012-01-18T09:34:46.851-06:00It's certainly not "EF's fault"....It's certainly not "EF's fault". This post wasn't meant to be an indictment of POCO/conventional solution providers. Is *is* meant to be an indictment of the idea that POCO/conventions will protect you from tight coupling and other design sins. That seems to be the implied message that a lot of people are sending, and it's just plain wrong.Chris Ammermanhttp://www.blogger.com/profile/13199328747453354231noreply@blogger.comtag:blogger.com,1999:blog-7442262522977329981.post-42035628816327399372012-01-17T12:41:42.303-06:002012-01-17T12:41:42.303-06:00Maybe this is because my experience is limited to ...Maybe this is because my experience is limited to EF, but if my POCOs exhibit the symptoms you talk about (e.g. loss of context/dilution of responsibilities) I don't think its EF's fault.<br /><br />Isn't it up to us to hold true to the vision of the architecture of our solution, even if the framework can make that difficult.Steve Duitsmanhttp://www.blogger.com/profile/10666232579579289254noreply@blogger.com