A group of senior Java engineers at Sun Microsystems has worked very hard to produce the Core J2EE Design Patterns. These patterns represent the best practices in J2EE design are one of the most important elements in industrialization of Java application development. The core design patterns allow developers to leverage the knowledge and expertise of Java gurus.
If your developers are refusing to use the core J2EE design patterns, try asking a few questions:
Are they able to produce a better design pattern than the recognized experts?
Will the non-standard design patterns be easy to read by third-party software developers?
Will it be possible to hire engineers with experience of their custom design patterns to reduce long term maintenance costs?
Will they document the design patterns as well as Sun has documented the Core J2EE Design Patterns?
What form of peer review process to they propose to prove their alternative design patterns are better than the core J2EE patterns?
The benefits of using the Core J2EE Design Patterns are only described very briefly, and perhaps understated, in the first chapter of the book Core J2EE Patterns: Best Practices and Design Strategies.
If professional application developers in a commercial environment want to re-write or redesign the core J2EE design patterns, I suggest that they are a) not focussing on real business problems b) have too much time available c) don't understand the realities of commercial software development and perhaps should consider an academic career. If they really have the time to design alternatives to the core J2EE patterns, it's time to downsize.
PJ Murray
CodeFutures Software
0 Comments:
Post a Comment
<< Home