121–130 of 373 posts
Seems to me that Java is also still one of the most supplied tech skills. So this does not necessarily make it a market you want to be in. Good SQL skills don't tend to be that common though, but I think a lot of the demand is more for CRUD-level operations than for complex analytics or performance-sensitive stuff.
In the recent two or so years I was surprised to see how many people don't _really_ know about SQL. Sure they can write a simple insert and update query and maybe a join, assuming they can just ignore that there actually are different types of joins. But if you ask them about other _still fundamental_ knowledge like a _rough_ idea about what the different transaction isolation level are/mean/imply for you, they fail…
I've always been frustrated by the promotion of this kind of list. Yes, it matters what the demand for a given skill is but that knowledge is virtually meaningless without also having information about the supply side! If 1,000,000 companies desire talent $foo which 2,000,000 workers have, it's not going to lead to as many opportunities or as much leverage as talent $bar that 300,000 companies desire but only 50,000…
I've been on projects with COBOL (yay!:), and there's always a complete dearth of skilled people...
I have to wonder if Java would be in demand if not for Android?
In the recent two or so years I was surprised to see how many people don't _really_ know about SQL. Sure they can write a simple insert and update query and maybe a join, assuming they can just ignore that there actually are different types of joins. But if you ask them about other _still fundamental_ knowledge like a _rough_ idea about what the different transaction isolation level are/mean/imply for you, they fail…
More a property of concurrency than of SQL, I believe; your point applies for programming languages too.
It's possible to get by as a programmer with no real understanding of how concurrency works in the relevant languages.
If concurrency bugs were always obvious, doubtless things would be different.
Earlier quoted context omitted.
The skill sets needed for the three big cloud providers are very different. At a high level it seems the same... VMs, VPC, Firewalls etc. but they all are configured and managed differently on each platform. You need the experience as an AWS, GCP or Azure expert.
Then it's disturbing that they're so non-standardized. I personally wouldn't want to spend a bunch of time becoming an expert in a skill that only applies to one company's physical servers.
> * Python is the third most common skill, posting strong growth driven partly by data science jobs.
> * Amazon Web Services (AWS), at number six, has had even more spectacular growth.
Source:
Indeed Tech Skills Explorer: Today’s Top Tech Skills https://www.hiringlab.org/2019/11/19/today's-top-tech-skills...
In the recent two or so years I was surprised to see how many people don't _really_ know about SQL. Sure they can write a simple insert and update query and maybe a join, assuming they can just ignore that there actually are different types of joins. But if you ask them about other _still fundamental_ knowledge like a _rough_ idea about what the different transaction isolation level are/mean/imply for you, they fail…
Regarding your 2nd point: commercial grade NoSQL db's can do all of these things now. I think the notion that they cannot is from the v1-2 era of Mongo about 7 years ago. You should read the Dynamo white paper and subsequent documentation on write consistency, transactions etc. and also look at the feature set available on Mongo V4.2.