The Source for Java Technology Collaboration

Home » java.net Forums » The Programming Profession » Your Java Career

Thread: A Server Side Career

Welcome, Guest Help
Login Login
Guest Settings Guest Settings
Reply to this Thread Reply to this Thread Search Forum Search Forum Back to Thread List Back to Thread List

Permlink Replies: 5 - Last Post: Feb 28, 2007 3:25 AM by: abickerton Threads: [ Previous | Next ]
bhills

Posts: 1
A Server Side Career
Posted: Sep 15, 2005 11:52 PM
  Click to reply to this thread Reply

Hi all.

I was wondering if anyone here during their Java career has moved from writing desktop Java to server side Java and how they did it.

I have been working on a desktop Java application for three years but this is now complete and there is no more Java work in the pipeline with my current employer and so I am looking to move on. Most of the Java jobs I see advertised here in the UK are for server side developers and this is the area I would like to move in to.

The problem is, all these jobs seems to require at least three years server side Java experience, but of course to gain this experience I need a job as a server side developer first! - So I am kinda stuck.

If anyone has any advice or has experience of moving from desktop coding to server side coding I would be very interested in hearing about it.

Thanks,

Ben.

pocarbuile

Posts: 3
Re: A Server Side Career
Posted: Sep 16, 2005 6:43 AM   in response to: bhills
  Click to reply to this thread Reply

Hi there,

IMHO, it's all in how you pitch yourself. I mean, I'm assuming that you've persisted data and that you've written service layers. That's much of the way to being a server-side developer. Read up a couple of O'Reilly books on, say, Hibernate and JBoss, run a couple of the examples, and you'll be well on the way to talking your way through an interview.


Patrick
--

edgriebel

Posts: 1
Re: A Server Side Career
Posted: Sep 16, 2005 8:34 AM   in response to: pocarbuile
  Click to reply to this thread Reply

Start by reading up on whichever server-side technology is being used so that way you'll be able to pitch in when the server-side coding is going slow.

Maybe you can start working on a widget that needs the back-end code done, and when you then get stuck, you casually suggest that you can work on the server side code too, knowing full well that you've already got most of it written :-)

mazzi123

Posts: 1
Re: A Server Side Career
Posted: Feb 26, 2007 10:11 AM   in response to: edgriebel
  Click to reply to this thread Reply

also read the negative side of software career as a whole
http://zoobka.com/story.php?title=Is-software-profession-is-more-stressed-one

jwenting

Posts: 478
Re: A Server Side Career
Posted: Feb 26, 2007 10:28 AM   in response to: bhills
  Click to reply to this thread Reply

I more or less slithered into it.
First Java project was a dataconversion to move data from a group of network servers to a mainframe.
After that I was the Java and SQL expert (not too difficult, I was the only one knowing both) for the company, and so when it was time to create a servlet based solution for a customer that would access their Oracle database I was the only one who could do it.

abickerton

Posts: 5
Re: A Server Side Career
Posted: Feb 28, 2007 3:25 AM   in response to: jwenting
  Click to reply to this thread Reply

After 4 years, of crummy jvm implementations with no debugging mechanism, extremely limited or downright unhelpful apis and obstructive device vendors. (It's another rant for another time) I'm in the process of moving back to Java EE from Java ME. Let me give you some pointers that helped me go back.
I don't know enough about your experience, my apologies if I'm stating the obvious.

1) Admit you don't know everything about coding. What basics you don't know, you can look up in the time between the interview and your first day. For the rest, there's Google and O'Reilly.
Bluffing through the interview won't get you anywhere but into trouble.

2) Read up on server-side technologies (Servlets / JSF, JSP, JDBC, XML, Tag libraries etc...), Don't worry too much about learning the api, make sure you understand what they are trying to achieve. Javadoc is for api reference!

3) It sounds obvious, but you'd be shocked how many people don't do it. Spend some time gaining practical experience with the technology. Setup the server software, run code examples, go through tutorials etc.




 XML java.net RSS