|We don't bite newbies here... much|
Re: Should I stay with this company or leave?by Booger (Pilgrim)
|on Nov 22, 2005 at 02:17 UTC||Need Help??|
I'm going to prefix this by saying that I don't know what sort of state your company is in, financially, management-wise or in relation to employee skill level or experience. There are many things that might drive your management to make a large and potentially unsettling shift in development like the one you mention but for the moment, take a look at this from the company's perspective.
I work for a software shop that caters to various aspects of the publishing industry. One product that we use is written pretty much entirely in RealBasic, the other project (the one that I am involved with) is written pretty much entirely in Perl. I've worked in several workplaces with different environments; Java, PHP, Sebiel and several other ugly beasts. I'm not trying to proclaim some sort of guru aura (I am not a guru, probably never will be either); I just want to say that I've been around a little. Impressed? I bet you would be: I even tie my own shoes!
Now for the record I'm pretty much enamoured of Perl. Perl is great; Perl is the mother-glue that binds us all together. Trouble is, some people (not necessarily you) spend so much time with Perl that their hands get sticky to the point of being unable to grasp other tools. This isn't the case because those people are unable to grok Perl but more because they find that other languages leave a bad taste in their mouth. I like to call this the Perl-does-this-better or Why-don't-they-do-this-like-Perl syndrome, often confused with the closely related My-way-is-better disease.
Here's my take on it (and please bear with me -- I'm about to over-simplify the situation):
A company's primary focus is to deliver solutions, services or products for their customers in such a way that they make their customers happy, thus generating a profit for the people who work for/own/have an interest in the company. I did mention that I was going to over-simplify this, didn't I?
Those languages that a company employs are, by and large, irrelevant to the company's primary focus. If a given language is perceived to be a barrier to a company's goals then a company will likely shift and try something else. What's the worst that could happen -- you might learn something new. Knowing how not to do a thing is at least as important as knowing the correct way to go about it.
After all, TMTOWTDI!