Comments on: Trade Offs: Some Thoughts http://www.markhneedham.com/blog/2009/03/02/trade-offs-some-thoughts/ Thoughts on Software Development Thu, 18 Mar 2010 23:35:30 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Challenging projects and the five stages of grief at Mark Needham http://www.markhneedham.com/blog/2009/03/02/trade-offs-some-thoughts/comment-page-1/#comment-21334 Challenging projects and the five stages of grief at Mark Needham Thu, 13 Aug 2009 07:23:04 +0000 http://www.markhneedham.com/blog/?p=987#comment-21334 [...] to problems may be suggested so we need to be aware of this and ensure that we think through the trade offs of new ideas before diving into [...] [...] to problems may be suggested so we need to be aware of this and ensure that we think through the trade offs of new ideas before diving into [...]

]]> By: Strong opinions, weakly held at Mark Needham http://www.markhneedham.com/blog/2009/03/02/trade-offs-some-thoughts/comment-page-1/#comment-20839 Strong opinions, weakly held at Mark Needham Sun, 02 Aug 2009 14:48:14 +0000 http://www.markhneedham.com/blog/?p=987#comment-20839 [...] latter seems to manifest itself when we don't explicitly consider the trade offs that always rear their head when making decisions in the world of software development and remain [...] [...] latter seems to manifest itself when we don't explicitly consider the trade offs that always rear their head when making decisions in the world of software development and remain [...]

]]> By: Coding: Quick feedback at Mark Needham http://www.markhneedham.com/blog/2009/03/02/trade-offs-some-thoughts/comment-page-1/#comment-20336 Coding: Quick feedback at Mark Needham Mon, 20 Jul 2009 11:11:13 +0000 http://www.markhneedham.com/blog/?p=987#comment-20336 [...] that I've come across where there are different ways that we can get feedback and we need to make trade offs to work out which is the best way for our given [...] [...] that I've come across where there are different ways that we can get feedback and we need to make trade offs to work out which is the best way for our given [...]

]]> By: Coding: Applying levels of abstraction at Mark Needham http://www.markhneedham.com/blog/2009/03/02/trade-offs-some-thoughts/comment-page-1/#comment-14864 Coding: Applying levels of abstraction at Mark Needham Sun, 19 Apr 2009 13:06:44 +0000 http://www.markhneedham.com/blog/?p=987#comment-14864 [...] think there is always a trade off to be made when it comes to creating abstractions - creating the abstraction adds to the complexity [...] [...] think there is always a trade off to be made when it comes to creating abstractions – creating the abstraction adds to the complexity [...]

]]> By: Phillip Calçado http://www.markhneedham.com/blog/2009/03/02/trade-offs-some-thoughts/comment-page-1/#comment-11619 Phillip Calçado Mon, 02 Mar 2009 23:53:15 +0000 http://www.markhneedham.com/blog/?p=987#comment-11619 I do believe that trade offs are required always but I find that your DDD example do not represent a case where this is actually required. Maybe the user has two different forms with the same data in the real world but the first thing to remember in DDD is that we are not trying to model the real world, we are trying to model a domain that the user understands and agrees with. In this case the most logical path would be to have an object representing this data and making both quote and policy share this instance. This is the usual OOP way of doing things and the only thing different in DDD is that this new class will have to be added to the ubiquitous language. cheers I do believe that trade offs are required always but I find that your DDD example do not represent a case where this is actually required.

Maybe the user has two different forms with the same data in the real world but the first thing to remember in DDD is that we are not trying to model the real world, we are trying to model a domain that the user understands and agrees with.

In this case the most logical path would be to have an object representing this data and making both quote and policy share this instance. This is the usual OOP way of doing things and the only thing different in DDD is that this new class will have to be added to the ubiquitous language.

cheers

]]>