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

In a recent JDJ article, Interviewing Enterprise Java Developers, the author, Yukov Fain, explained what J2EE developer needs to know. I really liked the article (you should read it), and author’s suggestions. Here is an excerpt from that article:

What does a good J2EE developer have to know in addition to understanding the difference between abstract classes and interfaces?

Usually employers are looking for people with at least 10 of the following skills:

• Java servlets,
• JSP,
• Struts or a similar framework,
• EJB,
• JMS,
• any commercial message-oriented middleware,
• JDBC,
• JNDI,
• HTML,
• XML,
• Ant,
• SQL,
• one of the major application servers,
• a couple of relational database management systems,
• any UML modeling tool,
• several design patterns (at least a Singleton!),
• and familiarity with Unix.

Next year JavaServer Faces and Hibernate will most likely be included in this laundry list.

What do you think? I think the list is reasonable. I know most of the technologies. No I don’t know all of them. I don’t know EJB, JMS, and I’m not really familiar with the applications servers. However, that’s on my to-learn list. I’m playing with JBoss, WebLogic, and WebSphere (hey, why not learn all of them ) Plus, EJB 3.0, which is coming up soon, is something I want to learn.

Are you completely clueless what those acronyms mean? Then it’s time to wake up. You better start reading and learning!