Two choices, Which one will you choose if you were me?
-
Choice C Move to a new job, which you decide what to program in.
.net is a box of never ending treasures, every day I get find another gem.
-
What kind of Java development? Seriously, it makes a difference. Java is a fine language but there is a lot more to Java development than just the language. If you get stuck in an EJB, J2EE situation then you might regret it. At work I face a similar situation (no narrow bosses though) and I have had to fight to make sure that we use Java smartly. In this case GRails and Groovy for web-dev.
regards, Paul Watson Ireland & South Africa
Shog9 wrote:
And with that, Paul closed his browser, sipped his herbal tea, fixed the flower in his hair, and smiled brightly at the multitude of cute, furry animals flocking around the grassy hillside where he sat coding Ruby on his Mac...
Paul Watson wrote:
What kind of Java development? Seriously, it makes a difference. Java is a fine language but there is a lot more to Java development than just the language. If you get stuck in an EJB, J2EE situation then you might regret it.
I don't know, that looks like develop add-ins for Office Programs.
-
Well break it down: Choice A: Learn a new language that is not in your comfort zone Choice B: Emotional intrigue from above and inside the department.
I would look at it as a chance to learn a new language that will give me insight to my favorite subject, programming. When you learn a new language, it gives you insights to the underlining ideas that govern all coding languages. The interaction between your code to the hardware and/or OS becomes clearer and clearer the more that you use other languages as well as your own preferred platform. Each language has standard techniques which can usually be applied to another language, giving you more tools to solve unique problems. As for the girl, just start a conversation with her, get to know her and start meeting her for lunch.
Once you realize that the only prison is your mind, you become free even in the most wretched of conditions -- Michael White
-
pete13mac wrote:
A bad manager is way worse than learning new technology, plus the new experience is always good for the resume. Many people leave a company because of a bad manager. It definitely detracts from the whole work experience.
Yeah, it is not easy to work together with a bad manager. But, this bad manager is not bad for everything. So it may be a chance to learn how to work together with a bad manager. and it may be good for my EQ.
pete13mac wrote:
Office romance definitely works better when you don't work directly together.
Can you explain more about this?
pete13mac wrote:
Good luck in whatever choice you make.
Thanks very much. and thanks for your reply. :rose:
If you date someone that you work with directly then there is more chance for awkward situations to arise if things don't work out or if one of you ends up managing/supervising the other. If you are in separate groups then you don't have to deal with office conflict or awkwardness.
Pete
-
I'm gonna get a lot of people kicking me in my ears for this one, just don't do until in bleeding out of them.. k? It's all about maturity. C# and most MS languages are VERY mature, why? Because these guys need to develop huge products, like Windows and Office, with the exact same tools (I have yet to see an OS, which ain't possible, or mainstream SQL database written in Java)... Oh, people might say that Microsoft is deviating from ANSI with MC++, but honestly, ANSI C++ was developed when? 1000BC? Are we still decorating caves with clubs? No, we are decorating classes with attributes. And please (and this is when I step on some toes), you will cry if you move to Java from C#. Imagine making a class for every event you want to handle, imagine not being able to write user-level threads... Back in the day when we still had programs that had 3 buttons and ran on a single CPU, Java was the [insert fowl rapper word here], and it has its uses (especially cellphone: but now everyone is going smartphone: MS C++/C# then). Java was a piece of art in the day. But why would you use a car to get to work if you could use a chopper? Microsoft just knows thier [once again]...
-
Learning how to negotiate your way thru bonehead managers is WAY more important than the language de jour. ymmv
-
Anton Afanasyev wrote:
Java is sorta similar to C# (ow, dont hit me with that..ow, that hurts ), well, to an extent. Quite east to learn the basics, and, well, the rest is online and easily findable.
It's not difficult to learn Java, but I think if I want to know Java deeply, it would spend me 1-2 years. but I would like to learn Software Design.
Anton Afanasyev wrote:
And, of course, depends on how much you dislike the manager in dept. B.
Very much. -- I didn't say one thing that is important, I like a girl in dept.B. ;P So I want to make closely to her. Thanks for your reply.:rose:
I wouldn't bring (a possible) office romance into the decision. It may never happen, or could be over in a short period of time... possibly ending with a lot of bad feelings. Then, you have to see that person every day. (Been there, done that, didn't like it.) However, if you are in different departments it could make the breakup a little less painful if it happens. I know I sound pessimistic, but I've seen these things go south more often than not. The choice between the language or the new department is a tough one. Which choice would further your career (if that's what you want)? What do you mean by the manager in dept B being narrow? Is it something you can or cannot live with? For me, all the cool tech stuff in the world won't make up for a bad manager, particularly one that micromanages. But if you do want to progress in the company, and manager B is tolerable, and your company has a career path you like, you may want to look into it. It sounds simple, but just make out a list of pros and cons for each decision. This can help put things in perspective a bit better.
-
I wouldn't bring (a possible) office romance into the decision. It may never happen, or could be over in a short period of time... possibly ending with a lot of bad feelings. Then, you have to see that person every day. (Been there, done that, didn't like it.) However, if you are in different departments it could make the breakup a little less painful if it happens. I know I sound pessimistic, but I've seen these things go south more often than not. The choice between the language or the new department is a tough one. Which choice would further your career (if that's what you want)? What do you mean by the manager in dept B being narrow? Is it something you can or cannot live with? For me, all the cool tech stuff in the world won't make up for a bad manager, particularly one that micromanages. But if you do want to progress in the company, and manager B is tolerable, and your company has a career path you like, you may want to look into it. It sounds simple, but just make out a list of pros and cons for each decision. This can help put things in perspective a bit better.
-
Choice A: 1, Learn a new program language - Java, I am familiar with MS languages, like C++, C#, VB, ASP.NET, but know little about Java. 2, If I want to stay in department A, I have to learn Java. Choice B: 1, Go to department B, because the languages department B used are MS languages. 2, But the manager of department B is a narrow guy, so you know... Which one will you choose if you were me?:)