3 ms·
Responding here since I can't respond to the grandchild comment of yours. You're right as far as experience of new graduates vs. those with 10 years experience
by nowarninglabel 13y ago
Responding here since I can't respond to the grandchild comment of yours.
You're right as far as experience of new graduates vs. those with 10 years experience (that basically, all either knows is Java), at least as far I experienced when I hired people when I worked for a university. However, the key difference between the younger set and the older set was that the fresh grads were open to and eager to learn new technologies whereas the older set basically gave me responses of: "Drupal, why would you use that?"
"PHP, that's horrible."
"That's not JSR-168 compliant"
And on... Now, you might say they were right to be skeptical. However, experience showed they were not. We did such a good job of replacing the old Java/Websphere/Oracle based systems for various university functions that we put a number of the Java engineers out of jobs without need to replace them (don't worry they were union so they just got transferred).
- learc83 13y ago>However, the key difference between the younger set and the older set was that the fresh grads were open to and eager to learn new technologies whereas the older set basically gave me responses of: "Drupal, why would you use that?" "PHP, that's horrible." "That's not JSR-168 compliant" That's partially because the younger kids didn't know enough to know what's wrong with PHP, but mostly because fresh college grads are so happy to actually have a job that they'll do anything to please. This isn't a case of the old guys not wanting to learn something new (PHP and java are almost exactly the same age). It's a case of old guys knowing enough about PHP to know that it has problems. Put it this way, if you want to hire someone to hit himself with a whip all day long, you find someone who doesn't know enough to know it hurts (or is a masochist).