tag:blogger.com,1999:blog-30926081.post4107452102078589250..comments2023-07-24T04:08:14.076-07:00Comments on Mitch Fincher: The Distracted Programmer: Agile Austin - Domain Driven Design and the Naked Objects PatternMitch Fincherhttp://www.blogger.com/profile/06517680094800899962noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-30926081.post-55108395942681251622009-11-26T11:15:38.533-08:002009-11-26T11:15:38.533-08:00hi this lea and i am doing a custom essays about t...hi this lea and i am doing a <a href="http://www.research-service.com/custom-essay-writing.html" rel="nofollow" rel="nofollow">custom essays</a> about the naked objects pattern i am very happy with naked objects now that they are connected . enforcing language domain is the right thing to do so keep it upAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-30926081.post-26792517836986485292009-11-05T04:03:24.044-08:002009-11-05T04:03:24.044-08:00Very glad that the Naked Objects message connected...Very glad that the Naked Objects message connected with you. You are absolutely right about forcing the domain language on the developer.<br /><br />I remember years ago hearing the architect Richard Rogers talking about the design of the Beaubourg - one of the first buildings that exposed all the services to view. He made the point that when you expose all the internals, you had better do them well. As we put it in Naked Objects, if the only thing the user can deal with is the domain objects then those objects had better represent the users world well.<br /><br />Take a look at Dan Haywood's new book: http://www.pragprog.com/titles/dhnako/domain-driven-design-using-naked-objects<br /><br />and also at Naked Objects for .NET if that interests you: http://www.nakedobjects.net<br /><br />Richard PawsonRichard Pawsonhttps://www.blogger.com/profile/01395737389966853357noreply@blogger.com