File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes Jobs Discussion and the fly likes Need advice ..... Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Careers » Jobs Discussion
Bookmark "Need advice ....." Watch "Need advice ....." New topic

Need advice .....

radha desai

Joined: Nov 28, 2006
Posts: 15

I am in a big dilema and seeking advice....

I am having 5+ exp in Java/J2EE tecnologies and working in one of India's top services company as a project leader.

Now my manager has asked me to shift to .Net as the product which we were working on is now shifting from Java to .Net.

I explained my preference about Java but he is reluctant to assign me something else.

Please advice me on what should I do? How shifting to .net will impact my career.

Thanks in advance.
Rahul Bhattacharjee
Ranch Hand

Joined: Nov 29, 2005
Posts: 2308
Change comapany if you do not like .Net .

Rahul Bhattacharjee
LinkedIn - Blog
radha desai

Joined: Nov 28, 2006
Posts: 15
its not about liking or disliking.

I want to knoww whether its worth shifting at this stage?
Shyam kumar
Ranch Hand

Joined: May 21, 2006
Posts: 146
Well I think it all depends upon your own carieer plans. If you want to become a project manager then it is in turn a greate opertunity for you to enhance your spetrum. On a long term basis, sooner or later you will end up doing somting like this once in a while.
But if your goal is to become an arcitect then make sure you do not stick with this project for more than 5-6 months.
But dont try to Changing job without giving a good fight.
Ram Deshpande
Ranch Hand

Joined: Feb 07, 2007
Posts: 51
I will suggest stuck with Java/J2EE.
Even if you shifted to Project Management Stream after 2/3 years, you will be in comfort position having excellent knowledge of J2EE.
You will have plenty of J2EE project so no need to go for any technology project mgmt.

In Architect stream, you need to be stuck for one Technology to get expertise in it. So J2EE is always good.

Go to you manager's Manager, discuss this issue and try to enforce your decision.

If not works, then only Change The Company


Out of clutter, find Simplicity. <br />From discord, find Harmony. <br />In the middle of difficulty lies Opportunity. - ALBERT EINSTEIN
Kj Reddy
Ranch Hand

Joined: Sep 20, 2003
Posts: 1704
I suggest use the opportunity to learn the .Net technologies. You are a Project Leader it will be added advantage for you knowing both .net & J2EE.
I have seen some big applications developed in multiple technologies like J2EE, C, C++, MS technologies for what ever reason. So when you are going to start work in that kind of applications your skill set will help you lot. Start working .Net for some time and if you feel uncomfortable then you can think about other options.

Good luck
Hendy Setyo Mulyo
Ranch Hand

Joined: Dec 01, 2004
Posts: 219

Yes. I also suggest you take this opportunity. It is good to have experiences in another technology, who knows you will learn something different that might strengthen your skill. But if this shifting takes more than 6 months, I think you better talk with your manager and if he still insists placing you in the project then it's your decision then whether you want to change company or wait untill the project is over.

Hendy Setyo Mulyo
SCJP 1.4 (95%), SCWCD 1.4 (94%)
william gates
Ranch Hand

Joined: Feb 21, 2007
Posts: 112
If you like your job, the company, and the pay, it makes a big different compared to if you hate where you work..

Maybe your company will move forward to .net and you learn to like it more than java and j2ee. Maybe you won't like it and move on. Who knows.

It's never a bad thing to learn something new.
Jignesh Patel
Ranch Hand

Joined: Nov 03, 2001
Posts: 626

In Architect stream, you need to be stuck for one Technology to get expertise in it. So J2EE is always good.


As an architect, my advice: there is nothing wrong to work in .net. It will give you different direction to think. And C# is no more different then Java, other then syntext and some missing goodies in java.
[ April 13, 2007: Message edited by: Jignesh Patel ]
Devesh H Rao
Ranch Hand

Joined: Feb 09, 2002
Posts: 687

Lead = A person who is responsible for the execution for a particluar subsection/or if the project is of a smaller estimate the whole project itself.

Architect = A person who is the solution owner and who lays down the guidelines for how the system/application should be architected for the business needs identified. Technology know how is important, but knowing more than one technology is more important.

Tech Lead = A person who is responsible for the technology fitment and complaince of the project.

Specialist Programmer/Developer = A person who knows the in's and out's of a particluar technology and is the "guru" on a particluar project, someone we all go to in case of an technical issue in the project

All four roles above being at the same level, unless you being a Specialist programmer a change in technology should be an asset rather than a bad thing. Even for an specialist programmer a new technology should be a learnin experience unless it is interfering too much with daily tasks.

Other than that an ability to learn newer stuff is always an addon especially at higher positions.

PS: I routinely reject people who show technology dependancy during interviews at levels of module lead/designer and above. This is a practise followed by many of my collegues as well.
Knowing more is never an issue. Not knowing that, knowing more is not an issue, is an issue.
[ April 14, 2007: Message edited by: Devesh H Rao ]
radha desai

Joined: Nov 28, 2006
Posts: 15
thank you all for your comments.
I agree. Here's the link:
subject: Need advice .....
jQuery in Action, 3rd edition