I don't want to learn your query language
&quot;Let’s dispel with the myth that ORMs make code cleaner. Join the embedded-SQL movement and discover a much more readable, much more straightforward way to query databases.&quot;<p>Any argument whatsoever for this?   Would love to see an example of how when you do away with the whole object persistence layer, and you just have a SQL string (which ORMs allow you to do anyway), how do you get your parameters over, how do you get your rows back, how do you manage your transactional scope, how do you get your rows in and out of your objects?   all of which has nothing to do with a SQL string.<p>Well let&#x27;s read on:<p>&quot;Erik Bernhardsson... is the CTO at Better, which is a startup changing how mortgages are done. I write a lot of code, some of which ends up being open sourced, such as Luigi and Annoy. &quot;<p>Open source stuff!  Let&#x27;s go there and see an example of this &quot;write raw SQL and don&#x27;t use any persistence libraries and your code is readable and straightforward&quot;, because nobody ever seems to actually want to illustrate this and how they don&#x27;t end up writing their own ORM anyway, and we see, oh <a href="https:&#x2F;&#x2F;github.com&#x2F;spotify&#x2F;luigi&#x2F;blob&#x2F;master&#x2F;luigi&#x2F;db_task_history.py#L48" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;spotify&#x2F;luigi&#x2F;blob&#x2F;master&#x2F;luigi&#x2F;db_task_h...</a>, it&#x27;s SQLAlchemy ORM.<p>Foiled again in my search to see this elusive super clean and simple raw SQL with no ORM that doesn&#x27;t reinvent an ORM anyway.   Which is the real &quot;myth&quot; ?