They used to say the problem with C (especially with respect to memory issues) was that people didn't know it well, which was also true to some extent, but then we realized that we could improve language design to not leave people in that situation in the first place. Something like Rust would have never materialized if people simply took the attitude that you just need to hunker down and know C harder.
SQL is ripe for a similar evolution, but such evolution is difficult when the only reason we settled on SQL in the first place was to be compatible with Oracle and Oracle has no reason to change as long as the money keeps flowing in. The competition was going down some other interesting paths for a while. Even Postgres originally used QUEL, which is much closer to Codd's original vision, instead of SQL but eventually had to accept that Oracle won. But does Oracle need to win forever?
Agreed with "one of", but the most common programming language is definitely Excel.
https://www.sql-workbench.eu/dbms_comparison.html
One day I just sat down and learned about every item on that table. Not memorizing, just learning what it was for. Not only did my concept of what you can do with a database expand dramatically but also the limitations of insisting on hacking up equivalents in your own application code.
It's amazing how many steps can be skipped and race conditions can be avoided by leaning into the SQL.
The right views, applied in the right places are like a super power compared to trying to do the same thing in application code.
Soon I discovered window functions so that I could, for instance, get my data back with an extra column with the total number of rows, or the data in the first and last rows, and so on.
These little things had a large impact on the number of lines of Java that I had to write.