Simplifying J2EE

The Pragmatic Craftsman :: Simplicity from complexity : by Stanley Kubasek ::

November 11th, 2004 | In Java | Comments Off

Do you think J2EE is complex? Do you think having many different frameworks, different APIs, and many different specifications help or hurt it? Do you think not having a single, one-way avenue for an inexperienced developer helps? I don’t. In this article, Simplifying Complexities of J2EE, Debu Panda gives you several arguments why J2EE should be simplified. I agree.

Share/Bookmark

Currently Reading

Me on Twitter

@leszekgruchala Good to hear it's fast. Looking to upgrade to IntelliJ 11 soon. - 2 days agoPutting related classes together is another way of looking at "structuring your code by feature." Makes your code more cohesive. Big + imho - 11 days agoplanetgeek.ch » Structure your code by feature - http://t.co/KcpMBKVg (via @sociablesite) #sociable - 11 days agoTell Congress: Don’t censor the web! http://t.co/ZEkgOAW7 - 18 days agoI must admit, I'm one of those developers that doesn't know too much about WeakReferences in Java. http://t.co/HjW7v9e0 Time to change that. - 19 days ago

The Pragmatic Craftsman :: Simplicity from complexity : by Stanley Kubasek ::