Comments on: Set Based Concurrent Engineering: A simple example http://www.markhneedham.com/blog/2009/09/19/set-based-concurrent-engineering-a-simple-example/ Thoughts on Software Development Tue, 16 Mar 2010 16:49:52 +0000 http://wordpress.org/?v=2.8.4 hourly 1 By: Knowing when to persevere and when to change approach at Mark Needham http://www.markhneedham.com/blog/2009/09/19/set-based-concurrent-engineering-a-simple-example/comment-page-1/#comment-26354 Knowing when to persevere and when to change approach at Mark Needham Sat, 07 Nov 2009 23:58:11 +0000 http://www.markhneedham.com/blog/?p=1653#comment-26354 [...] the task that there is some doubt as to which solution is the most appropriate then we can adopt a set based approach whereby we try out multiple potential solutions in [...] [...] the task that there is some doubt as to which solution is the most appropriate then we can adopt a set based approach whereby we try out multiple potential solutions in [...]

]]> By: Memory Profiling in Twisted Code with Heapy | Apparatus | DevBlogr http://www.markhneedham.com/blog/2009/09/19/set-based-concurrent-engineering-a-simple-example/comment-page-1/#comment-23336 Memory Profiling in Twisted Code with Heapy | Apparatus | DevBlogr Sat, 03 Oct 2009 06:35:09 +0000 http://www.markhneedham.com/blog/?p=1653#comment-23336 [...] Set Based Concurrent Engineering: A simple example at Mark Needham [...] [...] Set Based Concurrent Engineering: A simple example at Mark Needham [...]

]]> By: Mark Needham http://www.markhneedham.com/blog/2009/09/19/set-based-concurrent-engineering-a-simple-example/comment-page-1/#comment-22744 Mark Needham Fri, 18 Sep 2009 23:27:26 +0000 http://www.markhneedham.com/blog/?p=1653#comment-22744 Actually I'm planning to write about that bit as well but I didn't realise that it was part of set based concurrent engineering as well. Even if the library didn't have a bug in it I think given a similar situation in the future I would choose to use setter based injection because it takes much less time and the fact that we could mutate the dependency after creation isn't as important compared to that gain. Actually I'm planning to write about that bit as well but I didn't realise that it was part of set based concurrent engineering as well.

Even if the library didn't have a bug in it I think given a similar situation in the future I would choose to use setter based injection because it takes much less time and the fact that we could mutate the dependency after creation isn't as important compared to that gain.

]]> By: Jason Yip http://www.markhneedham.com/blog/2009/09/19/set-based-concurrent-engineering-a-simple-example/comment-page-1/#comment-22742 Jason Yip Fri, 18 Sep 2009 22:35:40 +0000 http://www.markhneedham.com/blog/?p=1653#comment-22742 One of the key aspects of the SBCE approach is the capturing of the knowledge in an appropriate form so the next time you need to make a similar decision you don't have to re-run the same experiment. One of the key aspects of the SBCE approach is the capturing of the knowledge in an appropriate form so the next time you need to make a similar decision you don't have to re-run the same experiment.

]]>