Comments on: Separation of Concerns by example: Part 4 http://lostechies.com/jimmybogard/2008/07/10/separation-of-concerns-by-example-part-4/ Strong opinions, weakly held Thu, 23 May 2013 23:40:00 +0000 hourly 1 http://wordpress.org/?v=3.4.2 By: Bryan Reynolds http://lostechies.com/jimmybogard/2008/07/10/separation-of-concerns-by-example-part-4/#comment-664 Bryan Reynolds Thu, 17 Jul 2008 16:50:11 +0000 /blogs/jimmy_bogard/archive/2008/07/10/separation-of-concerns-by-example-part-4.aspx#comment-664 Good example of seperation. Good example of seperation.

]]> By: Jeremy Gray http://lostechies.com/jimmybogard/2008/07/10/separation-of-concerns-by-example-part-4/#comment-663 Jeremy Gray Fri, 11 Jul 2008 13:57:05 +0000 /blogs/jimmy_bogard/archive/2008/07/10/separation-of-concerns-by-example-part-4.aspx#comment-663 I hear ya on the issue with changing legacy code, that's for sure. I hear ya on the issue with changing legacy code, that’s for sure.

]]> By: Jimmy Bogard http://lostechies.com/jimmybogard/2008/07/10/separation-of-concerns-by-example-part-4/#comment-662 Jimmy Bogard Fri, 11 Jul 2008 11:06:26 +0000 /blogs/jimmy_bogard/archive/2008/07/10/separation-of-concerns-by-example-part-4.aspx#comment-662 @Jeremy Gray Thanks! Unfortunately, Chad and Jeremy have a history of putting out just awful software. I pretty much distrust anything they put out. I mean, who builds an IoC container? It's called a constructor, duh! But seriously, it's a tough call to change the implementation of legacy code. With this snippet, the changes aren't very large. I'd have to carefully examine the impact of the change to make sure existing behavior isn't broken. In this case, it wouldn't be. @Jeremy Gray

Thanks! Unfortunately, Chad and Jeremy have a history of putting out just awful software. I pretty much distrust anything they put out. I mean, who builds an IoC container? It’s called a constructor, duh!

But seriously, it’s a tough call to change the implementation of legacy code. With this snippet, the changes aren’t very large. I’d have to carefully examine the impact of the change to make sure existing behavior isn’t broken. In this case, it wouldn’t be.

]]> By: Jeremy Gray http://lostechies.com/jimmybogard/2008/07/10/separation-of-concerns-by-example-part-4/#comment-661 Jeremy Gray Fri, 11 Jul 2008 01:46:01 +0000 /blogs/jimmy_bogard/archive/2008/07/10/separation-of-concerns-by-example-part-4.aspx#comment-661 Interestingly enough, this popped up all of a few days ago and I neglected to link to it the first time around: http://www.lostechies.com/blogs/chad_myers/archive/2008/07/07/exploring-shadetree-features-part-2-cache-lt-key-value-gt.aspx Interestingly enough, this popped up all of a few days ago and I neglected to link to it the first time around:

http://www.lostechies.com/blogs/chad_myers/archive/2008/07/07/exploring-shadetree-features-part-2-cache-lt-key-value-gt.aspx

]]> By: Jimmy Bogard http://lostechies.com/jimmybogard/2008/07/10/separation-of-concerns-by-example-part-4/#comment-660 Jimmy Bogard Fri, 11 Jul 2008 00:53:22 +0000 /blogs/jimmy_bogard/archive/2008/07/10/separation-of-concerns-by-example-part-4.aspx#comment-660 @jdn, Jeremy Yeah, that would definitely make more sense. That would likely be the next refactoring, as our behavioral specs are in place, we can make that change with confidence. @jdn, Jeremy

Yeah, that would definitely make more sense. That would likely be the next refactoring, as our behavioral specs are in place, we can make that change with confidence.

]]> By: jdn http://lostechies.com/jimmybogard/2008/07/10/separation-of-concerns-by-example-part-4/#comment-659 jdn Thu, 10 Jul 2008 20:43:58 +0000 /blogs/jimmy_bogard/archive/2008/07/10/separation-of-concerns-by-example-part-4.aspx#comment-659 http://scottcate.mykb.com/Article_5CB26.aspx http://scottcate.mykb.com/Article_5CB26.aspx

]]> By: Jeremy Gray http://lostechies.com/jimmybogard/2008/07/10/separation-of-concerns-by-example-part-4/#comment-658 Jeremy Gray Thu, 10 Jul 2008 13:55:51 +0000 /blogs/jimmy_bogard/archive/2008/07/10/separation-of-concerns-by-example-part-4.aspx#comment-658 Defining the cache interface with a TryGet (or similar), which jumped out at me in the earlier post, would also do the trick, and would additionally reduce duplication across usage sites (especially with a sprinkle of lambda) and allow for optimizations to be made in cache implementations. Defining the cache interface with a TryGet (or similar), which jumped out at me in the earlier post, would also do the trick, and would additionally reduce duplication across usage sites (especially with a sprinkle of lambda) and allow for optimizations to be made in cache implementations.

]]>