Comments on: The Layering Challenge http://almaer.com/blog/the-layering-challenge blogging about life, the universe, and everything tech Sat, 08 Sep 2012 07:06:53 -0700 http://wordpress.org/?v=2.8.4 hourly 1 By: Kirk http://almaer.com/blog/the-layering-challenge/comment-page-1#comment-17483 Kirk Sat, 05 Feb 2005 15:04:38 +0000 http://almaer.com/blog2/the-layering-challenge#comment-17483 I find that physical seperation (not having things avaliable to you) in the pysical layout of the code base helps to promote logical seperation (at the layer and component level). As much as it has gotten better, the Eclipse workspace doesn't support this type of thinking all that well. Bit off topic but the Eclipse workspace is a holdover from Smalltalk, one of the few concepts that should have not been transfered into the Java space ;) I find that physical seperation (not having things avaliable to you) in the pysical layout of the code base helps to promote logical seperation (at the layer and component level). As much as it has gotten better, the Eclipse workspace doesn’t support this type of thinking all that well.

Bit off topic but the Eclipse workspace is a holdover from Smalltalk, one of the few concepts that should have not been transfered into the Java space ;)

]]> By: Kirk http://almaer.com/blog/the-layering-challenge/comment-page-1#comment-17484 Kirk Sat, 05 Feb 2005 15:04:38 +0000 http://almaer.com/blog2/the-layering-challenge#comment-17484 I find that physical seperation (not having things avaliable to you) in the pysical layout of the code base helps to promote logical seperation (at the layer and component level). As much as it has gotten better, the Eclipse workspace doesn't support this type of thinking all that well. Bit off topic but the Eclipse workspace is a holdover from Smalltalk, one of the few concepts that should have not been transfered into the Java space ;) I find that physical seperation (not having things avaliable to you) in the pysical layout of the code base helps to promote logical seperation (at the layer and component level). As much as it has gotten better, the Eclipse workspace doesn’t support this type of thinking all that well.

Bit off topic but the Eclipse workspace is a holdover from Smalltalk, one of the few concepts that should have not been transfered into the Java space ;)

]]> By: Howard M. Lewis Ship http://almaer.com/blog/the-layering-challenge/comment-page-1#comment-17481 Howard M. Lewis Ship Fri, 04 Feb 2005 21:12:58 +0000 http://almaer.com/blog2/the-layering-challenge#comment-17481 I'll be responding to Kirk's article shortly. My basic answer to this is HiveMind ... it is an essential part of HiveMind that you can define your services at one layer, and provide the implementations at another. It is very reasonable to divide into layers and let HiveMind to the late binding to connect your choice of backend to your choice of presentation ... it just involves adding another layer of lasagne, I mean architecture, to abstract the relationship between the other layers. I’ll be responding to Kirk’s article shortly. My basic answer to this is HiveMind … it is an essential part of HiveMind that you can define your services at one layer, and provide the implementations at another. It is very reasonable to divide into layers and let HiveMind to the late binding to connect your choice of backend to your choice of presentation … it just involves adding another layer of lasagne, I mean architecture, to abstract the relationship between the other layers.

]]> By: Howard M. Lewis Ship http://almaer.com/blog/the-layering-challenge/comment-page-1#comment-17482 Howard M. Lewis Ship Fri, 04 Feb 2005 21:12:58 +0000 http://almaer.com/blog2/the-layering-challenge#comment-17482 I'll be responding to Kirk's article shortly. My basic answer to this is HiveMind ... it is an essential part of HiveMind that you can define your services at one layer, and provide the implementations at another. It is very reasonable to divide into layers and let HiveMind to the late binding to connect your choice of backend to your choice of presentation ... it just involves adding another layer of lasagne, I mean architecture, to abstract the relationship between the other layers. I’ll be responding to Kirk’s article shortly. My basic answer to this is HiveMind … it is an essential part of HiveMind that you can define your services at one layer, and provide the implementations at another. It is very reasonable to divide into layers and let HiveMind to the late binding to connect your choice of backend to your choice of presentation … it just involves adding another layer of lasagne, I mean architecture, to abstract the relationship between the other layers.

]]>