Live data from Hacker News

Today’s Top Tech Skills

hiringlab.org

321–330 of 373 posts

Re: Today’s Top Tech Skills

#322
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.

I am a mechanical engineer. Mechanical engineering jobs ask for SolidWorks/AutoCAD/CATIA/Creo/etc experience, not just computer-aided design; ANSYS/ABAQUS/NASTRAN/etc expertise, not just finite element method; Fluent/CFX/OpenFOAM/etc knowledge, not just computational fluid dynamics. With the exception of OpenFOAM, all of these software are proprietary, largely non-interoperable, and expensive—like thousands to tens o…

> I can only imagine tech companies would be more than happy to lead us to a future where software engineering is similar in this regard to other engineering disciplines. Perhaps this is what happens when a field matures, and since software is maturing, it will become more and more like this as the time goes on.

Actually software engineering had been like that for years in (distant) past. Most operating systems and compilers (that mattered for businesses) cost significant amounts. Not to mention access to computers.

It is said that Bill Gates' access to shared computers in his private high school [1] gave him advantage that very few people at that time could have had.

[1] https://www.cnbc.com/2018/05/24/bill-gates-got-what-he-neede...

Re: Today’s Top Tech Skills

#323
post #260

Earlier quoted context omitted.

With SQL, I started out using an ORM at my first internship and I've been using an ORM ever since. Over time, I've grown to dislike ORMs for anything more than anything trivial (a simple select statement with a handful of 'WHERE' clauses, an insert, or a delete). Most ORMs try to generalize the behavior between various RDBMS (Postgres, MySQL, SQLite, Oracle, MS SQL, etc.) and end up being exceptionally leaky abstract…

Could you describe what you mean by “leaky” in your experience?

For ORMs, the ORM is theoretically supposed to hide all details of the underlying RDBMS from the developer and only expose a set of common APIs. In actuality, you have to be acutely aware of the subtle differences between the various RDBMS and how they interact with the ORM. Generally the most frequently used functions are fine. But the less frequently used functions (which tend to be some of the most useful functions) may be dramatically different in behavior dependent upon the RDBMS [0].

For tools to generate a schema from code, the common data types are simple since the tooling is usually good enough to handle those common cases. But once you get into the non-trivial types (notably numerical types with custom scale and precision and timestamps), things go haywire very quickly. Another example is that all of the migration tools I've ever used have required the developer to define the model separately from the actual migration code which inevitably causes drift in the schema/migration code at some point.

Anyone that tries to define non-trivial relationships between tables/entities using non-SQL code is usually doomed to strange relationships in the RDBMS that'll make it arduous/near-impossible to ever use a different migration tool/ORM. I've seen some horrifying schema designs due to a near religious dependency on ORMs/automatic migration tools (foreign key references to the same table, join tables lacking foreign key constraints, columns intended to be foreign keys lacking a foreign key constraint, tables lacking in primary keys, etc.).

[0]: Notice how constraints are deferrable and adding comments onto columns are only available on certain RDBMS. https://sequelize.org/v5/manual/models-definition.html

Re: Today’s Top Tech Skills

#324
post #44

Earlier quoted context omitted.

You think? A huge chunk of work at Google is Java.

The median pay might be quite low for Java, because there are also a hojillion poorly-paid enterprise wageslaves toiling away in the cubicle farms. But the absolute number of people earning a lot (100k, 200k, whatever you think that is) might well be higher for Java than for anything else, because it's used in some significant big tech companies and in finance. So, if you're of average ability, learning Java might no…

I also think that the people at that wage consider programming language choice as a means to an end rather than a core skill.

Re: Today’s Top Tech Skills

#326

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…

You might be able to determine desirability by aggregating how long jobs are posted for or how many times it is extended. This would be a equate to some corelation.

Re: Today’s Top Tech Skills

#327

Java is still undisputed in the enterprise. Node.js was a contender but lost steam. May be .net once it becomes truly platform neutral have a chance to take on Java. Until then most probably it will remain widely popular.

Is it really your experience that node was ever a contender? In what context or application? Also enterprise is almost all windows on the client and on the server still has lots of traction; I don't see why .net needs platform neutrality to take a big piece of this. I find the numbers reported here pretty flawed; ".net" is down while "C#" is up about the same amount. I realize this data is based on keywords, so maybe…

Yes it was. That's why IBM, Microsoft etc rushed to adopt or sponsor Node.js. IBM acquired strongloop a NodeJs based enterprise framework. Microsoft extended their Chakra engine to support NodeJs but its still work in progress shows it lost steam..

Enterprises do not work with a brilliant language runtime, they need large ecosystem support from large vendors (read enteripse tools) and large availability of workforce, both of which are lacking in NodeJs esp. compared to Java. It's unfortunate as Typescript have now elevated NodeJs to a mature package and should have made stronger in roads into enterprises.

Re: Today’s Top Tech Skills

#328
post #16

Earlier quoted context omitted.

I figured that was mostly due to legacy code at this point; is it undisputed for new code too?

I've work for large national ISP where they are heavily trying to create a new series of network engineering tools (device discovery, adding new ARs with ease, upgrading existing devices, pragmatically change thru-puts between regions based on load, etc). Most of the backends for these types of tools would explicitly be done in Java. Why did they chose Java? Mostly because they would staff entire teams with H1Bs and…

Second that. Even the much advertised linked in uses Java engineers much more than NodeJs

Re: Today’s Top Tech Skills

#329

Earlier quoted context omitted.

I’ve hand written thousands of sql queries, including a year spent writing nothing but PL/SQL stored procedures. I’d fail your test, not because I’ve never used it but because I’ve not had to use it in years and, importantly, I rely on Google to remind me of syntax trivia when moving back to a language I haven’t actively worked in in a while. I HATE trivia questions and I’m convinced they are a sign of a lazy intervi…

It’s not a trivia question. It’s directly related to GROUP BY and is a core part of standard SELECT syntax. I’ve never met somebody who has spent any amount of time writing raw SQL who didn’t know it. I’ve met a lot who overly rely on their ORM but “have done a lot of SQL” who don’t.

Brightball, how many years of coding/sql/developer experience do you have?

Re: Today’s Top Tech Skills

#330

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…

Actually, they won't even test you on Skill X, if they are hiring for Skill X. They'll just make you take tests on Leetcode.

You are just better off skipping all this, and focusing on Leetcode interviews instead.

Post reply on HN