views:

172

answers:

7

Hi All,

I am currently working as a software developer mainly coding in PHP & JS at the current job. I have about 2 years of experience, mostly in web development and i am trained in Java. Have some basic work experience in Struts. I recently have 2 job offers. Both are respectable companies with leaders in their industry. IT & Logistics respectively.

The IT based company is offering me an System Analyst role and the Logistics company is offering me a programmer role. Surprisingly the Programmer role is a much higher paid job at about 25% more than my current job and the Analyst role is about 10% higher than my current job.

I love programming and i enjoy every bit of it. I have some fears of not able to return to a programming role after accepting a System Analyst role.

On the other hand, the Logistics company is using CGI-AWK and of course they are hiring me to work on CGI-AWK. My fear is that if i accept this role, i will be stuck to it and unable to move on to any other platforms or languages since CGI-AWK is really old school and i seriously doubt if any other company is using it.

I am at a crossroads now, having only 2 years of experience I still have plenty to learn. Looking at both jobs, which would be a more appropriate choice?

A: 

Follow the money. Then translate the cash into certification in a more up to date language. Then use the certification to get a job you actually want...

I think it's harder for a sys analyst to get into programming than for a current programmer to switch teams.

UPDATE
Quite frankly, I was a bit surprised by the comments I received on this, so I'm going to clarify my post.

First, if you want to be a programmer, stay in programmer like jobs. It's hard enough to get in, but, once in, it's easier to change languages.

Second, and more controversial, is my position on following the money. Jobs are temporary. Unless you are unionized or have some other form of protection, it's relatively easy to lose it. By the same token, they are generally fairly easy to get.

If the choice is between two jobs you aren't crazy about ( aka a Morton's Fork ), then pick the one you can more easily leverage into a job you do want. In this case, both the money and the continued work directly programming help provide that leverage.

If you do not choose to expand your standard of living beyond what it is now, then the money can be used to pay for books, training, tools (servers, compilers, etc), and anything else necessary to get a certification. Costs which could easily reach thousands of dollars.

Personally, I don't put much value on a certification itself; however, I do place a lot of value on the hard work it takes to get it. If you are actually dedicated to this, then the training materials will only be one part of your education and acing an interview in a new job hunt will be easy. Further it will give you a solid foundation to build on.

I am a firm believer in working hard and smart now in order to enjoy the fruits of your labor later. Sure the higher paying job means working in a language you may not enjoy but it is only a means to an end. While at the job actually take the time to understand the language used. Programming is as much an art form as it is a job; and knowing other languages (even the crap ones) only strengthens you. The experience you gain will show you exactly why people cringe at it AND give you the knowledge necessary to evaluate which path you want to choose for your future.

Finally, unlike others here, I am not threatened by the success of others. In fact, I feel that our industry as a whole only gets better when colleagues take the time to truly educate themselves in order to provide a higher standard of practice. Further, I am sickened by the sheer number of people I run into that really have no clue what they are doing, or worse, try and hold others back for fear of their own position.

Regardless of the path you choose, I wish you well and am delighted that you are consciously trying to pick a future. Too many people just fall into this.

Finally, I am a programmer, and I own my own company. So take the above as coming from both a colleague and a potential future employer.

Chris Lively
-1: I disagree with the first point; but agree with the second.
Jim G.
I don't care whether it's put into practice, but it's world-destroying point of view.
Pavel Shved
@Jim, the money is in the programming job. Both points kind of go hand in hand.
Chris Lively
@pavel: in what way? Make more money, get better training, get a better job, make more money, rinse and repeat as necessary... It's kind of how things work.
Chris Lively
@Chris, as a high-gifted person, I strictly object the way "things work" that provides ungifted persons with the way to get better jobs than me. Someone else would even give economical explanation, but I won't; I think what I said suffices.
Pavel Shved
You don't need more money to get better training. It's also probably not a good idea to spend your life doing things you don't really want to do so that maybe someday you'll be able to do what you want.
Amuck
@Amuck: Sometimes you do need the money to pay for the training. I don't know his current financial situation, but there is obviously a reason why he even interviewed jobs outside his normal work to begin with.
Chris Lively
@Pavel: You object because getting training mean that this guy ends up making more than you? Talk about world-destroying. Are you just peeved that you haven't done it? Gifted or not, our field needs qualified people. And one of the best ways of doing that right now is through training and certification. I would love to see bron succeed. And, quite frankly, am more willing to hire someone that has done everything in their power to get into a particular job than someone who thinks they walk on water. The later ones usually flame out and have a much harder time adapting to change.
Chris Lively
@Chris, I am trying to add a positive vote to your post but i am not sure what what happened there. Keep getting the vote too old to change. I fully appreciate your answer and your time in taking to answer the question, gives me another perspective to look at. Yes, the monetary side is definitely a huge bonus, i am hesitating because of the odd/old platform involved.
bron
@Chris: +1 for taking the time to explain your position. I disagree with your position of sacrificing working environment for money. However, I think your idea of "following the money" is good, because a place that pays you more will, in general (exceptions are banks) value you more and want to make better use of your skills and intelligence.
Larry Watanabe
+2  A: 

Take the programmer job.

As a programmer, you always need to be constantly learning. With that being said, I'd encourage you to learn new languages and frameworks in your spare time.

In this economy, no job is forever. With that being said, choose jobs that will develop skills that will help you along your desired career progression (which will be subject to change).

In sum, if you have any inclination to program, choose the programmer job.

Jim G.
+4  A: 

If you can, I would reject both offers and wait until I got one doing what I wanted to do. Not knowing your situation, it's hard to say if you can wait, but if it is possible, that's what I woudl do. No amount of maney is worth a job where you are miserable.

HLGEM
+1: So if bron was playing 'The Oregon Trail', you'd advise him to "Wait for conditions to improve".
Jim G.
A: 

Any chance there's a Door Number 3 floating around? I agree that the Systems Analyst job is probably not what you want, but CGI-AWK - are these people from the Stone Age?

One possibility is to take the programming position and then get all OSS-subversive on them. Maybe do something cutting edge with Perl 2.0 :-)

Seriously, if you can show alternate ways of doing things they may finally see the light. On the other hand, these people may be Morlocks and might eat you for your efforts.

Peter Rowell
A: 

I can't believe the Logistics company is hiring you only for working on CGI-AWK and nothing else, or do they really? If you will have a chance to use new tools for new code, take the programmers job.

Doc Brown
+3  A: 

Go with the programmer role. The higher pay is a clue that you will be doing more challenging work for that company, otherwise they would just hire someone cheaper. Don't go for an empty title -- "Systems Analyst" -- if the job really was at a higher level than the programmer role, then it should pay significantly higher.

Don't worry about using outdated technology. Programming skills transcend language and frameworks. By the time you move onto your next job, there will probably be some other technology around that hasn't even been invented yet that will be in demand, and all the stuff you would have learned that is hot today will probably be "deprecated".

Larry Watanabe
+1 for programming skills transcends language and framework. Made me feel spiritual.
whatnick
+2  A: 

If programming is your passion, then take the programming job. I'd think it worth following your heart here and recognize that there is a lot to each job that isn't likely to be found until you are knee deep into working someplace. Chances are there are other hazards in each job, but there is also something to be said for trying a new role for a couple of years and seeing what happens. You don't know that next week or next year they will only be using CGI-AWK, so why worry about being shackled to it forever at this point?

Course as I say that I've gone through various changes too. From C++ ISAPI extensions to classic ASP to ASP.Net which has been some shift in the last 10 years and I can wonder what will the next 10 years bring.

JB King