This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Few months back I had asked a suggestion through this thread.https://www.coderanch.com/t/599974/Jobs/careers/career-suggestion-decision I had got useful suggestions and implemented those but now situation has become deeper.
I was a java resource who had worked in Indian company for 4 years on java-j2ee.Then the asked me that they want me to work on hadoop also.I worked thinking there is java too in that E.g Map-Reduce, Hive-JDBC but it is very little java and one might get out of touch ,still I did.I used to practice java by self applications at home on Saturday Sunday.But now they have changed my domain from Java to DataWharehousing. After learning java from all these years is if i start switching to datawarehousing now it is difficult for me and of not much use i think. When I was in java it was easier for me as I have been doing since few years.Now in datawharehousing i struggle whole week.Please suggest me whether I should change company or is it possible to get out of datawahehousing in same company or another way?
"Big data" is a growing market, along with DWH, business intelligence, analytics etc. But many Java-based service suppliers have been very poor at providing high quality database skills to their customers. Now the Java market has matured - some might say it is saturated - some companies are looking for new markets, such as DWH. This might mean that you will have more opportunities as somebody who knows about data and Java than if you only know about Java. Of course, if you don't like working with data, or you don't want to move outside Java, then you will need to decide whether to move back into the familiar world of Java, but you should consider how far that might affect your future career options.
No more Blub for me, thank you, Vicar.
Joined: Jul 07, 2012
I understand Data Wharehousing is Good but I have been working in java since around 5 years and in datawharehousing I have to start and build a confort level which will take lot of time.I want to go to office and do somehting which I am comfortable with. As an experienced resource you are expected to deliver fast. Since I have been working in java I can in java but in datawahrehousing I have to struggle a lot and do. Please suggest is is possible to switch off from it in same company or I have to switch my company.? and how to do that.
Monica. Shiralkar wrote:I want to go to office and do something which I am comfortable with.
I recommend you find a different way to explain your preferences to your manager, because it sounds like you basically don't want to have to learn anything new outside your "comfort zone", which is not a good attitude to have in a fast-moving industry like IT. Maybe you can find areas within Java that you want to explore further and that would also be useful to your company. If so, make this your "official" reason for wanting to change.
Monica. Shiralkar wrote:As an experienced resource you are expected to deliver fast. Since I have been working in java I can in java but in datawahrehousing I have to struggle a lot and do.
Any reasonable manager would recognise that if they put you to work in a new area, it will take time for you to get up to speed. But if you are finding it really difficult. it may be that you need extra training/support, or maybe you simply don't have the aptitude for it. Only you can decide that.
Monica. Shiralkar wrote:Please suggest is is possible to switch off from it in same company or I have to switch my company.? and how to do that.
It will depend on your company and your managers. If your manager is approachable and flexible, you may be able to discuss the matter constructively and find an alternative area of work where you feel more comfortable. But you need to find a more positive way to present your concerns - you can't just say "I want to go back to Java because it's easy!". Your company pays you to work, not to relax, and if they need people who can do Java + DWH, but you can only do Java, then they may decide that you are less useful to them. Alternatively, you may need to find a different job, but you will still need to find a way to "spin" your reasons for changing jobs, so start thinking about how to explain your career goals in a more positive way.
Joined: Jul 07, 2012
The concern is that since my domain has been changed from java to data wharehousing, the next projects which I will get in this company will be in Data Warehousing instead of Java.I wanted to get Java work in future too? Is that not a problem?
Monica. Shiralkar wrote:The concern is that since my domain has been changed from java to data wharehousing, the next projects which I will get in this company will be in Data Warehousing instead of Java.I wanted to get Java work in future too? Is that not a problem?
Not necessarily. Working on a data warehousing project gives you skills in the space of data. These are good skills to have. (I think it is great your company is offering you the chance to learn a new skill on the job.) You could become the "data" expert on a Java project and do a mix of coding/tuning/etc. Or pretty much anything. It's hard to predict the future.
As other posters have mentioned, its better to have a mixed bag than only specialized in specific languages, or for some people, even frameworks.
Rather than being in comfort zone and probably repeating things in a big loop over the years, working on engineering challenges will definitely do good for your career, as it would help you stand out from the masses.
I think it also depends on what you enjoy working on and if you're willing to sacrifice certain perks for it. If you're fortunate and if you've planned things really well, you might get things without sacrificing anything. But sometimes you've got to refuse. Refuse as in say... NO. You must weigh all the probable outcomes before you do that.
Sometimes we've got to take small, little risks.. And this can be difficult. Weigh what you'd be losing against what you will definitely gain, and what you might gain.
Data warehousing is good stuff to know as it seems to me from what people have suggested. So you are good. You don't need take the extreme step.