251–260 of 373 posts
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.
My guess is that Node.js either saturated the market of web developers looking to do backend, or people realized that type safety is a good thing, and JS doesn't have a good story for it.
The surprise is not that Java, C and C# are still ranked highly but that their share grew in the last 10 years. It underscores the difference between (at least my) perception and the market reality.
Also we shouldn’t forget C# has a resurgence on many fronts not least unity and as a very good nodejs replacement these days.
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 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.
I'd actually be really pissed if a company asked me to write a query like "count these orders by month in a single row" not because I couldn't do it but because I'm confident I'd screw up the syntax a couple of times.
I think they should ask more conceptual questions around set theory or storage structure, epsecially since they all want "SQL, SQL Server, Oracle, Postgres, etc". Nobody can stay on top of all the platform specifics, but someone who knows their stuff can answer the udnerlying problems.
Earlier quoted context omitted.
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.
Lol. Are you new to technology or something?
Earlier quoted context omitted.
I figured that was mostly due to legacy code at this point; is it undisputed for new code too?
If your systems are Java, you'll hire people who can work in Java, and if the only thing your devs have in common is experience with Java, your new code will be in Java too.
I was pleased (somewhat) 20 years ago when Java displaced C++, but now I just wish it would fade away.
Thanks for the garbage collector, Java, now retire.
This said as someone who is convinced that most of what I want to do could be done with FP vs OOP techniques, and FAR less of it.
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.
C# and CLR lost it a few years ago, GraalVM is taking this space really rapidly now.
I'm in opposition to most comments here hating Java for whatever reason, hoping JS or C# to destabilize this system. I absolutely love Java and its ecosystem. Super mature libraries, library for everything, great tools, literally for everything. A lot of tutorials, massive investment from several corporations contributing to OpenJDK. Java is super hot right now.
Earlier quoted context omitted.
because price ( aka salary / fee) is a function of supply and demand and it grows the more the skill is in demand. As simple as that. Let’s say you want to start a career as a freelance for example : what skill to you put forward ? You may say « but jobs requiring elixir are probably more interesting than sql/java ». I agree, but that is if there’s one position open at the time you’re looking , in the area you’re loo…
It isn't that simple. Most "Java + SQL" jobs are run of the mill cost-center type jobs at companies that aren't tech companies. Their salaries, benefits, and locales are generally poor relatively to other software engineering jobs. The demand is high, and so is the supply of labor, but that isn't the whole picture.
Seems an even trade.
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…
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…