Comments on: Refactoring an established Domain Model http://lostechies.com/seanchambers/2008/06/22/refactoring-an-established-domain-language/ Just another LosTechies site Thu, 13 Sep 2012 07:11:00 +0000 hourly 1 http://wordpress.org/?v=3.4.2 By: Sean Chambers http://lostechies.com/seanchambers/2008/06/22/refactoring-an-established-domain-language/#comment-249 Sean Chambers Mon, 23 Jun 2008 00:55:10 +0000 /blogs/sean_chambers/archive/2008/06/22/refactoring-an-established-domain-language.aspx#comment-249 True, what I meant to say was, if you slack on communication and feedback rather than "cut" True, what I meant to say was, if you slack on communication and feedback rather than “cut”

]]> By: Joe Ocampo http://lostechies.com/seanchambers/2008/06/22/refactoring-an-established-domain-language/#comment-248 Joe Ocampo Sun, 22 Jun 2008 20:53:11 +0000 /blogs/sean_chambers/archive/2008/06/22/refactoring-an-established-domain-language.aspx#comment-248 >If you cut this portion out of the loop you increase risk very quickly... I wouldn't say this is an option. You cannot cut this if you are doing Domain Driven Design. Communication and feedback are essential to DDD. To remove it would be like putting together a model without the glue. Sure you could try to get it to work but in the end it would all fall apart. >If you cut this portion out of the loop you increase risk very quickly…

I wouldn’t say this is an option. You cannot cut this if you are doing Domain Driven Design. Communication and feedback are essential to DDD. To remove it would be like putting together a model without the glue. Sure you could try to get it to work but in the end it would all fall apart.

]]>