tag:blogger.com,1999:blog-1383695822029623916.post5440078576711836937..comments2024-03-28T00:20:38.908-04:00Comments on Chris Wong's Development Blog: Let's get rid of middle managementChristopher Wonghttp://www.blogger.com/profile/16941177380839071164noreply@blogger.comBlogger8125tag:blogger.com,1999:blog-1383695822029623916.post-84622888499970434622011-03-23T21:51:41.814-04:002011-03-23T21:51:41.814-04:00I was reviewing this blog and wondered if you can ...I was reviewing this blog and wondered if you can elaborate on your elimination of interfaces, layers and adapters as it relates to the maintainability of an application as the following occurs: 1) New people join the team and need to learn the structure without having to know all the different components and what each does? 2) New front end consumers of a service are developed, such as Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-1383695822029623916.post-48728154540857209452010-03-31T03:43:01.479-04:002010-03-31T03:43:01.479-04:00Amen!Amen!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-1383695822029623916.post-52265834759163041592010-02-12T02:44:54.277-05:002010-02-12T02:44:54.277-05:00My experience is that in non-trivial cases it'...My experience is that in non-trivial cases it's better to have levels: UI class -> Service -> DAO.<br /><br />Alas, I need to have also Service and DAO interfaces if I want Spring proxies without cglib.<br />And usually I really need those proxies because I use Spring aspects for logging bean calls performance.<br /><br />But in some 50% cases the code in layers is a trivial forward altumanohttps://www.blogger.com/profile/07644069616370903161noreply@blogger.comtag:blogger.com,1999:blog-1383695822029623916.post-75817257467953887322010-02-11T09:17:43.979-05:002010-02-11T09:17:43.979-05:00Excellent post, and I agree with most everything s...Excellent post, and I agree with most everything said.<br /><br />When I'm working on a personal project, I've completely stopped using interfaces for a service/persistence layer. <br /><br />I'm not here to bash ORM, but I'm not really a fan of Hibernate/JDO/JPA, etc. So I personally wouldn't do away with a DAO layer. What if you needed multiple DB operations within a Derrickhttp://www.profeval.comnoreply@blogger.comtag:blogger.com,1999:blog-1383695822029623916.post-5191214650053652422010-02-10T11:41:01.327-05:002010-02-10T11:41:01.327-05:00Excellent post!!!
As for this statement:
"P...Excellent post!!! <br />As for this statement: <br />"Personally, I am not completely settled in how to balance the ideals of doing it "right" by enterprise Java standards and getting things done in a relatively straightforward way."<br /><br /> It's VERY IMPORTANT that you don't even think too much about the "Java" way when it comes to getting things done asTerrynoreply@blogger.comtag:blogger.com,1999:blog-1383695822029623916.post-40865028220499859422010-01-26T21:56:53.708-05:002010-01-26T21:56:53.708-05:00I think those middle management give you some flex...I think those middle management give you some flexibility to build automated test cases. Without them, you probably have to setup a fake datasource<br /><br />or, I am wrong?CARFIELDhttps://www.blogger.com/profile/13094952618057460795noreply@blogger.comtag:blogger.com,1999:blog-1383695822029623916.post-66394405073035447192010-01-26T10:08:06.246-05:002010-01-26T10:08:06.246-05:00I too have seen this emerge many times in my caree...I too have seen this emerge many times in my career. While Spring is great, the mindset that they push has only made things complicate unnecessarily. I remember IBM pushed a framewok called pandoora on the USDA. What a disaster. Something like 7 or 8 layers. I'm glad I personally got over the notion that things had to be complicated and lots of indirection just to do something simple.<br /><Annoyedhttps://www.blogger.com/profile/17205687004036552519noreply@blogger.comtag:blogger.com,1999:blog-1383695822029623916.post-46785989239182556592010-01-25T09:45:17.453-05:002010-01-25T09:45:17.453-05:00I think the observation of the middle management d...I think the observation of the middle management design pattern in Java server side follows directly from flaws in the language itself. Java makes it very difficult for one class to be used differently in different contexts (model classes in form vs. persisted objects, api classes in unit tests vs. integration). Dynamic, object oriented languages such as Ruby and Python have taken big strides Pete Brattonhttp://poweredbythepete.wordpress.com/noreply@blogger.com