The author has a point, and Sql is good when it is a human interacting with the database (that's what it was designed for after all). But when it comes to sof

The author has a point, and Sql is good when it is a human interacting with the database (that's what it was designed for after all). But when it comes to software/library interacting with the DB it is simply terrible. Some times you just want to say say hey, give me this specific data and in that case Sql is the easiest solution. But if you have more complex model and you have a bunch of parameters and you need to build one or more queries based on these parameters then you are better off with ORM. I think that's actually how the first ORMs got started, people got tired building queries with strings.