Yeah. The mismatch between how devs expect to use the ORM, and how the ORM expects to be used, causes enough problems in my experience to make the ORM not worth

Yeah. The mismatch between how devs expect to use the ORM, and how the ORM expects to be used, causes enough problems in my experience to make the ORM not worth it in the first place. I'm tired of seeing crazy-long NHibernate stack traces and exception descriptions because, like, a column got altered. Writing data-retrieval code is tedious, and nerds always want to automate tedious things. But sometimes the cure is worse than the disease, and the effort to eliminate one type of tedium gives rise to a new, fancier kind of tedium.