> You apply one of eight abilities to the lemmings, which all have obvious uses but can also follow on and interrupt each other to offer new possibilities. This is a really good point. Lemmings was one of the earliest…
Knowing whether to `SELECT *` vs `SELECT a,b,c` is the entry-level/babys-first-optimization case. Providing a high level and performant ORM, takes deep knowledge of the underlying database and a lot of code complexity.…
I’m not saying developer-friendly APIs are bad, but i do think hand-crafted, well-written, and well-tested SQL outperforms any ORM, and if any ORM comes close to the performance of hand-crafted queries, it does so at…
Of course, all of this goes completely out the window if your company mandates an ORM for database access, which i feel it’s pretty safe to say about 90% of companies do. But that’s the point of ORMs. Disregard anything…
> You apply one of eight abilities to the lemmings, which all have obvious uses but can also follow on and interrupt each other to offer new possibilities. This is a really good point. Lemmings was one of the earliest…
Knowing whether to `SELECT *` vs `SELECT a,b,c` is the entry-level/babys-first-optimization case. Providing a high level and performant ORM, takes deep knowledge of the underlying database and a lot of code complexity.…
I’m not saying developer-friendly APIs are bad, but i do think hand-crafted, well-written, and well-tested SQL outperforms any ORM, and if any ORM comes close to the performance of hand-crafted queries, it does so at…
Of course, all of this goes completely out the window if your company mandates an ORM for database access, which i feel it’s pretty safe to say about 90% of companies do. But that’s the point of ORMs. Disregard anything…