Languages vs. Platforms?
andyfsu99 inputs: "Recently I've noticed the increasing confusion between Java the language and Java the platform. Recruiters and project managers routinely ask for a numeric "rating" of a developer's Java skills. Do they mean Java the language (OO concepts, syntax, libraries, etc)? Or Java the platform (EJB, JCA, JSP, etc)? How do you answer this question? Clearly, Sun is pushing the platform definition. How will this effect the evolution of emerging techologies like C# and .NET? Will major new languages be forever coupled with platforms moving forward?"
FP!
propz to all dead penis birdz
-PT5K
Having said that, relevant experience is important. If I'm doing all server work, and I have one guy with 5 years doing all Swing and client side GUI stuff, and another guy with 5 years doing J2EE, then you can call it language or platform all you want, but I call it relevant experience. That's nothing new. The same rules apply as they always have -- sure, maybe the Swing guy has enough experience with the language that he can get up to speed in the new domain, but I will likely save time by hiring the guy who is more familiar with the platform. However, if my 5yr swing guy is up against a 6month J2EE guy, then I would be more likely to take the gamble on the Swing guy.
www.HearMySoulSpeak.com
Since when do recruiters have any idea what they are talking about?
If you understand EJB's and J2EE in general, odds are you have a good OOD background. But I still think that design (specially OO) is one of the most crutical skills to have, so don't exclude that.
Good quote, too many chars. Seriously, the slashdot 120 char limit sucks!