If you start as a young rookie learning new things all the time, you can learn to adapt. If you start refusing to do things at your age because it's not "java", that might have serios problems when your 40, and have been doing Java for 20 years, and don't know anything else. Learn java, become great at it, but don't just dismiss stuff you think is "not cool or useless" because sometimes you never know what tomorrow brings.
Originally posted by Harry Kirsten:
My work is basically, using the APIs provided by the SalesForce platform in these several technologies and then built the solutions.
Originally posted by Theodore Casser:
I suppose that I look at it that way since I'm in a very similar position - for the last five years, I've primarily been working with a different COTS product (OpenText's Livelink). However, in the course of working with it, I've also made sure to keep learning things outside of work when the work I do at the office isn't expanding my knowledge - you never know when something else might crop up - which goes along with what Stephen was saying about making sure you learn as much as you can.
But, to go with what I was saying... I don't know that the concentration is of itself a bad thing.
Originally posted by stephen gates:
In the long run, you try to make your employer happy. If they want to use Salesforce, then learn it and become good at it. If you want to learn ruby or ejbs, do some side projects, buy some books, learn it, then see if there is any way it could be implemented. Learn about different methodologies, learn about different technologies.
Watchya got in that poodle gun? Anything for me? Or this tiny ad?
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koophttps://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton