From the article, about why mitigations of these issues is not viable: > Likely they will require increased understanding of the specific ORM being used So y

From the article, about why mitigations of these issues is not viable: > Likely they will require increased understanding of the specific ORM being used So your diagnostic of "deliberately avoid reading the documentation" is spot on. If the goal of the author is to not read the docs, I completely agree that most ORMs are an absolute hell to use and going back to almost pure SQL would be the holy grail. But then, I am personnally in the camp of spending the time to understand the tools. There is a tradeoff between the time spent to on learning a specific tool and the ROI of that learning curve, I think this article's position on wanting mostly returns with no time invested is way too unrealistic.