Job Postings For Python, NoSQL, Apache Hadoop Way Up This Year
Nerval's Lobster writes: "Dice [note: our corporate overlord] collects a ton of data from job postings. Its latest findings? The number of jobs posted for NoSQL experts has risen 54 percent year-over-year, ahead of postings for professionals skilled in so-called 'Big Data' (up 46 percent), Apache Hadoop (43 percent), and Python (16 percent). Employers are also seeking those with expertise in Software-as-a-Service platforms, to the tune of 20 percent more job postings over the past twelve months; in a similar vein, postings for tech professionals with some cloud experience have leapt 27 percent in the same period. Nothing earth-shattering here, but it's perhaps interesting to note that, for all the hype surrounding some of these things, there's actually significant demand behind them."
It seems strange to specifically ask for experts that know no SQL.
Sure, they'll post the job. Like posting a job for folks who have four years experience driving Chevy pickups. As if you can't learn the skills they want in two weeks.
But it lets them pretend there's a "skills shortage" while leaving millions of qualified workers begging for hire.
Percentages can be very misleading, do they have raw numbers?
If there was only one python posting last year but 10 this year, that's 1000%!!!
especially for working remotely.
LPNAH just isn't the same.
"First they came for the slanderers and i said nothing."
It could be the typical PHB gets sucked into the hype and tosses those buzzwords into the job ad to make sure he's getting the "freshest talent". The ad is already stuffed with gazillion buzzwords, so why not gazillion + 1
Table-ized A.I.
Sure, the job may say "Python" or "PHP" in the title, but .... they usually want niche skills with some CMS you've never heard of written in these languages, and if you read the whole job writeup, it's not a "Python" job other than you need to know Python to write extensions for the CMS. So if you know Python programming, you still won't get the job.
The reason why there's a "shortage" of skills at the same time there's a glut of developers available is the insanely narrow specialization that companies want. There aren't many people who have even heard of the CMS-of-the-week the company uses, let alone knows its internals well enough to do what the company wants done. Companies seem very good at picking losers in the technology race, and get stuck with things that are evolutionary dead ends, further limiting their talent pool.
Big data is probably the same thing, but I don't know anything about it.
work performed by people relying on these folks to do their jobs falls dramatically. IT support staff frazzled at having to constantly find solutions to problems created by people who are supposedly wizards at what they do.
IT management oblivious to problems so long as products get shoved at door and they can make their bonuses.
We will bankrupt ourselves in the vain search for absolute security. -- Dwight D. Eisenhower
Those were all niche markets a couple of years ago so big percentage increases don't mean all that much.
IMHO...most companies won't ever have a use for Hadoop. "Big Data" is a buzz word that doesn't mean anything. "Cloud" doesn't require a specially trained expert. NoSQL is another word for caching, which most enterprisy applications don't do well, so that's worth knowing (especially if the app is trying to use Java/Hibernate for persistence, yuck). Python will continue increasing in popularity because there isn't a better alternative for quick scripting and small applications, Java is too cumbersome for small tasks.
I wonder how many of those jobs for "big data" involve data sets that will sit on a USB drive?
PHB: "But it's a TERABYTE, at least!"
I have no problem with your religion until you decide it's reason to deprive others of the truth.
What is CMS?
How is NoSQL another word for caching? You can use NoSQL databases to implement cache systems, but that in no way is the extent of it (the term itself is very, very vague and means a multitude of different approaches to handle data).
(the term itself is very, very vague and means a multitude of different approaches to handle data)
Yes, that's a big part of the problem. But when you listen to the reasons to use NoSql they all come down to having the data stored in a manner the application can get to it quickly, with less consideration given to the usual RDB concerns like data integrity and normalization. To me, that's a cache (although "cache" is also a vague term).
Content Management System
Actually to me NoSQL means firstly schema-less data and not ACID operations. But then there are NoSQL DBs that allow defining schames and have ACID operations.
But try to explain that to your average recruiter.
In search of Big Data Engineers in S Florida! Let's talk tech! http://lnkd.in/dbKtwW9
Please contact me @954-541-8451 Adriana