Job statistics XXVII : Java/J2EE uber alle????

[john bailo]

she said he said she said asj said,

the question is, why? is it because companies bought a lot of java stuff
during the dotcom days and now need people to maintain the things, OR
are we still seeing lots of new projects? with the economy the way it
is, i'll bet ya it's the former.

wrong-a-mundo

java has just become more of a standard, so whereas before you
were seeing 'experimental' java projects, now we are dealing with
entrenched production systems that require skilled java coders to
upgrade and maintain them.

 

[Alvin Bruney]

how about this
java is so buggy and slow and companies don't have the capital to rebuild
from scratch using dot.net so they hire java programmers to maintain the
mess. until money makes itself available to rewrite it in dot.net. that ='s
more short term java jobs.

 

[asj]

how about this?

the dotnet hype died (and with it microsoft's plans of using c# to kill
java) and companies are continuing to pour money into the one scalable,
cross-platform, and robust enterprise solution out there - J2EE.

plus, some companies that started on dotnet (e.g. eBay, Cerner) decided
to switch to J2EE, creating more jobs for Java developers.

bwahahahabwahahaha!!!!!

 

[Guest]

COMMENT INLINE BELOW:

except of course none of his points addresses the fact that there seems
be a hell lot more java jobs than anything out there.

There is a difference between a "java job" and a "java *FAKE* job posting".
UNDERSTAND???

Just because you see a POSTING does NOT mean it's a REAL JOB.

Recruiters hear that Java is pain in the butt and then think that they can
make more off the java programmer. Recruiters then keep POSTING, POSTING,
POSTING in order to be ready to FILL this so-called JOB that doesn't exist
YET only in their dollar sign $$$ eyes. Do you see how that works? Does
that explain why there are MORE java POSTINGS? It's like a LOTTERY to
recruiters. Recruiters buy TICKETS, a.k.a Job Postings, to hit that ONE
job that will make their quota or monthly rent, that's how desperate they
are.....

RULE ONE:
YOU cannot tell via JOB POSTING which technology is better because it ONLY
TAKE ONE RECRUITING AGENCY to LIE and POST FAKE JOBS OVER and OVER and OVER
AGAIN, AGAIN, AGAIN.


Hmmm. YOU sound like the investor who kept buying ENRON even after all the
investigations and even after they declared bankruptcy AND said, LOOK, LOOK,
LOOK at the NUMBERS they are putting out...they don't LIE.

 

[asj]

COMMENT INLINE BELOW:



There is a difference between a "java job" and a "java *FAKE* job posting".
UNDERSTAND???

Just because you see a POSTING does NOT mean it's a REAL JOB.

booohooohoooo.......

mi amigo, you cannot use that as an ABSOLUTE measure of the job market,
BUT you can use all those job banks as a RELATIVE measure of the demand
for different technologies and platforms.

perhaps even your brain can understand that?

ONE job bank saying one thing and another saying another might cause
some confusion, but the fact that multiple INDEPENDENT job banks show
the same thing does give some credence to it. here it is again: YOU
CANNOT MEASURE ABSOLUTE DEMAND BY IT, BUT YOU CAN INFER RELATIVE DEMAND.

in addition, you have this as well:

SkillMarket - Languages
A daily look at in-demand tech skills
http://mshiltonj.com/sm/categories/languages/

 

[Tim Tyler]

: SkillMarket - Languages
: A daily look at in-demand tech skills
: http://mshiltonj.com/sm/categories/languages/

SQL is beating Java there :-(

IBM's crappy database lanugage form the stone age continues its zombie
existence.

http://mshiltonj.com/sm/categories/technologies/ is less favourable
still to Java - it has .NET beating J2EE.

I'm not sure why .NET (a general framework) is being compared to
J2EE (a third of the J2ME, S2SE, J2EE trinity) in the first place -
but even so, it doesn't look good.