4 ms·
ORMs are like any technology choice, they allow you to get by with less-skilled engineers. You have to work with the tools you are given, and if the only readil
by vinceguidry 10y ago
ORMs are like any technology choice, they allow you to get by with less-skilled engineers. You have to work with the tools you are given, and if the only readily-available devs to hire in your area are all .NET guys, guess what your tech stack is going to look like?
Trying to make these decisions based on the merits of the techs themselves doesn't derisk the business, it does the opposite.
- diminoten 10y agoI think the problem people have with ORMs includes the fact that it seems like it should let you get away with less-skilled engineers, but the more skilled engineers know that the ORM doesn't save nearly as much time/knowledge as it appears to. It's true, you can have a junior person write up a view simply using the ORM as it appears, but then during code review it'll be valuable for the senior person to come in and say things like, "That query is going to suck, here's how you'd get that data without locking so many tables."
- gnaritas 10y agoIf any of your queries are locking tables find a better database; what a senior would do is look at the query log and say hey, you've got an N+1 cascade load issue causing this to be so slow, optimize the query to prefetch the sub data or create a view that has the data you need already and map that. Cascade lazy loading is usually what makes an ORM perform badly and it's merely an indication the dev has a query to optimize, not a sign the ORM is broken.