tags:

views:

223

answers:

9

Hi There,

Folks , kindly I need some guidance or advice for selecting job.

Got two options ,

1) A job with dot net coding plus with php knowledge. Its private firm.

2) Second is, C coding ,which is technical and engineering side based.

My aim is to study further (not excluding money requirement, of course that is necessary ) , I doesnt know much about market nowadays.

Need some advice for opting job.

Thanks

A: 

I don't think the decision to join a firm should be based on what programming language they use (although if you really hate Microsoft stuff, you might shy away from .NET).

As a software engineer, you ideally want to know and learn a few set of languages and should be proficient enough to be language neutral.

I would recommend looking at the benefits/advantages the company offers along with the money. There is nothing stopping you learning new technologies outside of work (if you are really passionate about learning), however, a good employer will factor learning into your role.

Sarat
+1  A: 

Can I say "refuse both"? :)

C is a very old language (almost 35 years, now), surpassed by C++ in primis. PHP is "spaghetti language for the web" when it comes to maintainability and scalability.

I'd accept one of those (maybe the .net one) but, once inside, I'd try to push the company/project to new technologies.

friol
C is still very much in use in embedded systems and hardware control.
David Poole
I have to play devil's advocate here. What is it that makes "old language" mean "bad?" That's not to say that I would necessarily go with C myself. But I don't think that C's biggest problem is its age.
Jason Baker
Lisp and Smalltalk are old too, but I'd rather use those (at least their modern forms) than a lot of newer languages.
Chuck
I somewhat agree with the comment.
Dmitri Nesteruk
I also agree. There are many other languages invented in the 1970's that are a distant memory. C has remained stable, useful, and popular because it solves a legitimate need. See how far you get asking the Linux community to rewrite their kernel in Haskell.
Bill Karwin
+3  A: 

I'd take the job where I like the people I will work with best.

But then I come from a background (Switzerland) where changing jobs often is not so easy and potentially frowned upon, when in the CV. YMMD

lexu
A: 

Only you can make a decision that makes sense for you. Take into account:

  • Your current skilss (do you feel comfortable with C? .NET? PHP?)
  • Skills you would like to develop (would you like to go into .NET? systems?)
  • Payment
  • and your overall interest in the project

No one can tell you which is best... I would easily go for C/Systems :)

João da Silva
A: 

Well, if you're looking to study further, etc., it seems like job #1 would be you're best bet. Right off the bat, you're working with two different paradigms (.net and php). That's a good start.

A: 

If your main goal is to learn something, I'd recommend going with the C job. That's not to say that C is the most fun language to program in, but rather that your future employers will probably view experience with C the most favorably. This may even apply if you end up wanting a job in the future that involves PHP or .Net. The fact of the matter is that C gives you an idea of what's going on in the background behind the other programming languages that do more for you.

Jason Baker
A: 

If your looking for a job where you can expand your knowledge, Your best bet is option one. The .net stack will allow you to work with a object oriented language and an evolving framework. The asp/php have a lot of blogs and books available to help you further your skills, Its also possible to take this experience and apply it to Java development.

Aaron Fischer
+2  A: 

Go with your gut, its usually right.

I had a planned severance situation a couple of years back and I ended up with six job offers. I used a very complex pros/cons method of determining which job to take. I ended up taking the job that made the most "sense" using a variety of hard factors (compensation, commute, benefits, flexibility, industry, size/stability, etc). However, I also had a funny/bad feeling about the one I ended up taking. Within a week after I started, I realized I would never really enjoy working there. The funny thing is, my manager was great, I got to work from home once a week, the compensation/benefits were really good, and I was working on an important project using the latest tools. But the corporate culture just wasn't a fit for me and I wasn't happy.

I left 9 months later for a work-from-home for a small company gig I'm still at now.

JohnOpincar
+1  A: 

My five rules I use to judge a job, in no particular order.

  • good work environment (decent office and equipment)
  • good coworkers (are the people nice? good to work with?)
  • good prospects for the future (is there a future with this technology and/or company?)
  • good work (is the work fun and rewarding?)
  • good pay/benefits

The underlying technology doesn't really matter. Languages change, tools change, platforms change.

David Poole