Why use ORMs if LLMs write code?

The return of SQL? It's no secret that I'm no fan of ORMs. Most people, on the other hand, find them indispensable. As one reader commented: "I can work with raw SQL ofcourse... but the mapping... oh the mapping..." qfilip This seems to capture something essential. When I discuss ORMs, the most common argument in favour seems to revolve around the amount of boilerplate code required to communicate with a relational database. And indeed, it's significant. As I've argued, however, I'm not convinced that ORMs solve that problem. But now that LLMs write code, does it even matter? In addition to my individual reservations, it strikes me that ORMs come with many issues related to query efficiency. The vibe I'm getting from ORM experts is that if you really know a particular ORM, you can fine-tune the queries it makes. There are, however, various pitfalls to avoid: Anti-patterns to eschew, idioms to follow, particular APIs to keep clear of, certain parameter values to explicitly pass, etc.…