Turning hours into minutes, and minutes into seconds.
When someone falls from a bike, the responsibility lies not with the bike or cycling, but with lack of skill, carelessness, choosing the wrong road, inappropriate equipment, or neglecting adverse but predictable circumstances.
 
When you turn you car on, do you worry about the year the wheel was invented?
Or simply use it until they come up with something better?
Yes, this is also true for SQL.
For decades, teachers and pseudo-gurus, with no experience in the market, have defended the rejection of SQL, teaching that:
"a programmer's time is more expensive than a computer's time", a fallacy based on the disregard of several factors, such as:
The negative impact of slow code on the business, the useful life of a
system and, the wrong assumption that programming in SQL is unproductive, finally, the dreaded Cloud bill.
 
"When all you have is a hammer, the screw becomes a nail."
 
 
Your database is designed to be agile and reliable, but if it is not properly configured and oriented, the result will be slowness and disappointment.
They try to solve everything with ORM, and when reality emerges,
It's time to venture into SQL. However, the lack of technical
skills and the constant change of programmers do not help with maintenance of code developed based on the principle:"We learn by doing".