The Pragmatic Craftsman :: Simplicity from complexity ::

«
»

Simplifying J2EE

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.

Comments are closed.

Random Quote

Topics

Tags

Archive

Recent Entries

  • Staying Sharp
  • Make fields final, objects immutable
  • Beginning Java EE 6 with Glassfish 3
  • Java EE 6 – Job Well Done
  • Java Inner Classes – Part 4 – Multiple Inheritance and Closures
  • Java Inner Classes – Part 3 – Nested Classes
  • Java Inner Classes – Part 2 – Anonymous
  • Java Inner Classes – Intro
  • What makes a great software engineer?
  • Design Patterns Explained

    • Currently Reading

    Shelfari: Book reviews on your book blog

    :: The Pragmatic Craftsman recommends

    :: The Pragmatic Craftsman book reviews

    Info

    © 2001-2010 Stanley Kubasek About me :: Contact me

    @PragCraftsman on Twitter

    I put Code Complete #1 over Martin's book because it has "awaken" me as a programmer. But other than that, Martin's book is the best! - 6 hours ago@mcory1 First of all, @unclebobmartin is my hero! Agile Software Development, Principles, Patterns, and Practices is my #2. SOLID rules! :) - 6 hours agoWhich programming book has had the most influence on your career? I have to say "Code Complete" by McConnell - 19 hours agoI have not used Git myself, but see a lot of good buzz about it. Is this anology accurate: Git is to SVN as SVN is to CVS? #git #svn - 1 day ago