6 replies to this topic

[Root23]

This isn't so much a coding question, as a general job question... What should someone looking to get an entry-level position know?

I'm graduating in December (2year AAS degree), in which I've taken two Java classes. However, I don't feel I would be able to jump into an entry-level position. My second Java course used Introduction to Java Programming (Y. Daniel Ling), and we maybe covered half of that book.. in which half of that was just review of things we covered in my first Java course. (Tip: If your school loses their Java2 teacher, and knows a semester in advance, but waits until 2 weeks before the start of the semester to hire a new Java2 teacher... RUN! It's going to be a chaotic/unorganized nightmare.) I'd love to find the time to go through that book more thoroughly.. as I feel it's a good book. In the mean time, what would be good areas to concentrate on and make sure I understand well?

You experienced guys, or those that just started as an entry-level developer... What do you expect the entry level guys to know, or what did the hiring manager expect you to know?

I've been more focused on finding an entry-level front-end web development job lately because I'm more confident working with those technologies... but ultimately my plan is not front-end dev.. I'd like to find a job as a java developer.

Edited by Root23, 31 May 2011 - 07:46 AM.

[gregwarner]

The one thing I've used more than anything else in Java is database connection API's. Get to know Oracle's JDBC API and optionally MySQL's Connector/J API intimately. Also, brush up on your Database best known practices, such as Index Organized Tables and any other little optimization things. It's important to understand these concepts and to know the proper time to use them. That's my 2 cents. :)

[Root23]

I was thinking that's would be something I should know, that was never mentioned in either of my Java classes. Well, my Java 1 teacher said it was something that would be covered in Java 2. We didn't.

I'll make sure I read through that chapter in my textbook and work on several of the programming exercises that are at the end of each chapter. I was actually hoping to take an Oracle DB class in the fall, but it interfered with the JSP class I also need to graduate, so I'm taking TransactSQL instead.

My plan is to continue reading through my text book (and reread a few chapters we already covered), and just start doing several of the programming exercises from each chapter. I just wanted to have an idea of which chapters I should make sure I focus on more.

So far..
1. Database Connection APIs

[wim DC]

Aren't ORM (object-relational-mapping) frameworks often used in combination with JPA so you don't really have to care about different databases?

[gregwarner]

Read the highest voted answer on this page to see why I don't use ORM's:
What Java ORM do you prefer, and why? - Stack Overflow

[wim DC]

A bit more constructive for the OP, maybe ^^.
I think java web applications are also commonly used. Guess it never hurts to know how to build / call a web service with Java... How to build a web site/application with it.

[gregwarner]

But bringing up the topic of the ORM frameworks brings up a valid point:

Whatever corporation you work for will set the standards for what languages/frameworks you use. Unless you are in a leadership position, which takes years to achieve, you will likely be following the coding standards set by your project managers. This means, if your company has standardized on one particular ORM framework, then that is the framework you will code in. Or, if they have elected to go with the bare DB connector API's, then that will be your technique.

I guess the point I'm trying to make is, better than saying that one particular framework or API is what you should learn before going for a job, is the reminder to remain flexible and willing to learn. The best technique to learn before going into a new job is how to learn. (Sorry if this answer is too "meta"). :)