I felt that ORM systems were negative 15 years ago. They have improved quite a bit since then. An increasing number of competitive frameworks have come out and the incumbent frameworks have improved. The situation is much better than when that "Vietnam" article came out. I think many people use a lightweight ORM such as Colander and if you are happy with that, that is great.
These days though I am using SQL very differently than the old days. I used to use MySQL, PostgreSQL and sometimes Microsoft SQL Server but lately if I use SQL it is SQLite. Today I am much likely to use some kind of graph or document database such as DynamoDB or OpenLink Virtuoso, but it has been a long process to get confident enough in the new tools.
What I see missing from most db tools is the ability to map functions from the host langage to the query language in back. For instance, if you write something like
lambda x: 5x-2x*x+7
you should be able to compile that the SQL or SPARQL or whatever equivalent. Microsoft's LINQ framework approaches that with a lot of specific features built into the runtime and language. In either Python or Java you can run a (or the) compiler/decompiler on an expression, make an AST, convert that AST into a query AST and send it to the database engine.