[ajug-members] Entry Level Java Jobs
brian_a_lee at hotmail.com
Fri Sep 24 11:37:02 EDT 2004
Note, I didn't say that you "must" use frameworks, just that you "must"
consider them and have an excellent reason not to use them.
For example, if you go into an interview and tell an architect that you
don't like struts and prefer straight JSP/Servlets then you need an
explanation. "Struts wasn't invented yet" is an excellent explanation. But
Struts is not complicated or heavy and actually takes less time then just
writing Servlets and JSP so even small projects can benefit from it.
Of course legacy systems shouldn't be torn up and re-written just because
there's newer tech out there (which I didn't advocate in my original email
:) just look at all those COBOL apps still lingering around.
I think that understanding and having experience in commonly used frameworks
is essential to finding and retaining a job in the Java/J2EE space.
>From: "Jack J. Coleman" <jackjc at bellsouth.net>
>To: "General AJUG membership forum (100-200
>messages/month)"<ajug-members at ajug.org>
>Subject: Re: [ajug-members] Entry Level Java Jobs
>Date: Fri, 24 Sep 2004 09:54:24 -0400
>I disagree with your statements about web and persistence frameworks. Just
>because there is a new, and in your mind "better" technology that surfaces,
>does not mean that the entire Java world should abandon the basics. I work
>on a number of projects that do not use the frameworks you mention. I guess
>there is a problem with me then. Using a framework just for the sake of
>using it is not reason enough. Frameworks add a level of complexity that
>vanilla JSP/Servlets and JDBC do not have. Especially on smaller projects,
>I see no reason for using a framework (other than "oh that is a cool thing
>to have on my resume, so I'd better try it out"). Even on older, larger
>"legacy" Java projects that are working fine with JSP and JDBC, there is no
>business justification (in my opinion) on spending the time and money to
>"upgrade" to one of these frameworks.
>You are right, however, that the bane of Java is the ever increasing number
>of libraries, API's, specs, etc.
>Brian Lee wrote:
>>Struts (or some other major web framework) is required for web apps
>>nowadays. If you're still writing apps in JSP/Servlet there must be some
>>pretty major reason you aren't using Struts/Cocoon/Spring/WebWork/etc.
>>I also think the same goes for JDBC, if you're writing straight JDBC
>>instead of using Hibernate/iBATIS/BC4J/JDO or even EJB without some
>>serious consideration then there's probably some problem with the
>>architects at your site.
>>Also, 2 years ago although EJB wasn't required, if you didn't know when
>>and where to use EJB then my clients wouldn't have hired you. EJB isn't
>>the end all be all, but it has purposes and a good developer/architect
>>needs to know when and how to use them.
>>The tough part about Java seems to be it's constant evolution and new OS
>>libraries coming online. It's a full time job to keep up with new stuff
>>and expect to be master some new Java/J2EE tech every 1-3 years.
>>I for one welcome our new JSF overlords :)
>ajug-members mailing list
>ajug-members at ajug.org
More information about the ajug-members