Live data from Hacker News

Today’s Top Tech Skills

hiringlab.org

21–30 of 373 posts

Re: Today’s Top Tech Skills

#21
I have always found this quite amusing that every company I have ever applied to for a job has SQL in required skills and yet not a single one of them has ever interviewed me on it.

Re: Today’s Top Tech Skills

#22
post #17
post #14

It remains weird and disturbing to me that "AWS" is treated as a skill. Not "cloud system management", but " AWS ". Edit: I do understand why it can be lucrative to have expertise with a specific cloud provider. It's just the status quo of these services being their own unique silos that disturbs me: I would personally be wary of making "ability to effectively use Amazon's servers" a pillar of my career.

No weirder than putting "Java" instead of "Object Oriented Programming"

Not really. Using Java doesn't come with having to have a relationship with a company (beyond the the JDK EULA nobody reads or cares about anyway).

Re: Today’s Top Tech Skills

#24
post #14

It remains weird and disturbing to me that "AWS" is treated as a skill. Not "cloud system management", but " AWS ". Edit: I do understand why it can be lucrative to have expertise with a specific cloud provider. It's just the status quo of these services being their own unique silos that disturbs me: I would personally be wary of making "ability to effectively use Amazon's servers" a pillar of my career.

There’s a lot of details to learn before you can manage a complex aws set up. Sure someone with “cloud system management” skills can ramp up on those details. But if you need someone to be productive right away, you want to hire someone that already has them at his or her fingertips. And in a world where people jump ship every year or two being productive right away is pretty important.

Re: Today’s Top Tech Skills

#25
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 hard.

Realizing this allowed me to understand why:

1. There is so many used ORM(ish) libraries which make it in practice harder to access the database for anything but trivial queries.

2. NoSqlish databases seem to have became so successful even in application where non of there "benefits" (wrt. scalability and similar) matter and you would normally prefer to avoid some of there drawbacks (e.g. eventual consistency, no "system wide-ish" transaction, enforcement of correct schemata and some parts of data consistency). (Sure there are other reasons for there success, too. Like being fancy, modern or no clear requirements analysis and therefore no idea about scaleability requirements ...).

I mean if SQL and relational databases are for you just structs with a bit more basic types then JSON but which in turn are flat requiring annoying foreign key references and a bunch of ceremony around this with very little added benefits then yes it makes so much more sense to just use a nosql database and be done with.

(PS: Yes I'm aware that for certain use-cases the resulting databases can be very complex and hard to use, what I mean is that it's a skill you have to learn to use efficiently and a scarily large amount of people a came in contact with in the recent years not only don't have that skill but are not aware that, if they don't want to mess up larger databases they work on, they will have to learn that skill.)

Re: Today’s Top Tech Skills

#26
post #15

I’m thinking about the future. What skills will dominate the software market 10-20 years from now? - Big companies use C++ heavily, besides being the language for deep learning/GPU programming. Will Rust/Go replace it anytime soon? - Will React still dominate front end development? - What about Python and the data analysis ecosystem?

Old, boring, battle tested.

Re: Today’s Top Tech Skills

#27
post #14

It remains weird and disturbing to me that "AWS" is treated as a skill. Not "cloud system management", but " AWS ". Edit: I do understand why it can be lucrative to have expertise with a specific cloud provider. It's just the status quo of these services being their own unique silos that disturbs me: I would personally be wary of making "ability to effectively use Amazon's servers" a pillar of my career.

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.

Re: Today’s Top Tech Skills

#29
post #17
post #14

It remains weird and disturbing to me that "AWS" is treated as a skill. Not "cloud system management", but " AWS ". Edit: I do understand why it can be lucrative to have expertise with a specific cloud provider. It's just the status quo of these services being their own unique silos that disturbs me: I would personally be wary of making "ability to effectively use Amazon's servers" a pillar of my career.

No weirder than putting "Java" instead of "Object Oriented Programming"

Yes, it is. I can build anything in Java and run it on any computer owned by anybody. AWS isn't a technology, it's just Amazon's computers and the constraints and interfaces they wrap around them.
Post reply on HN