3 ms·
Not a great question for the stated purpose. Some people will dig in to the various tradeoffs involved with an ORM, and pick apart the structure of an ORM. And
by ben509 7y ago
Not a great question for the stated purpose.
Some people will dig in to the various tradeoffs involved with an ORM, and pick apart the structure of an ORM. And that should result in an "it depends" kind of answer.
Others are more interested in how a team is going to use an ORM; does it help junior devs write "not awful" code, how does it help me structure my application logic.
Others are stats nerds who will tell you which ones do best on benchmarks, are most popular, etc.
And many people will tell you a story about some ORMs they used, and why they liked them or not.
These answers can be useful for getting a sense of how a person thinks, but they won't tell you if the person is competent.
- xwdv 7y agoThe competent person will say all ORMs are garbage.
- deleted 7y ago[deleted]
- Mike8435 7y agoSimplistic "No True Scotsman" bullshit. ORMs provide type safety, ease of refactoring, and reduce a lot of boilerplate. Of course, occasionally you need to bypass an ORM to write complex queries, which is fine. ORMs are not perfect, but are a very useful tool nonetheless.
- tcbasche 7y agoIronically a competent person would probably not say "All X's are garbage" because, as with most things in software, it's a) complicated and b) never that clear cut.