One of the most salient features of our Tech Hiring culture is that there is so much bullshit. Everyone knows this. Each of us contributes his share. But we tend to take the situation for granted.
"I want to fetch all users living in Berlin drinking coffee".
How to best implement this? The nice thing is that you can mostly let SQL figure this out, merely giving him indications that you will use often this index to do searches.
Imperative programming is micro-management: do this, then do that, then do this, then do that.
One of the most salient features of our Tech Hiring culture is that there is so much bullshit. Everyone knows this. Each of us contributes his share. But we tend to take the situation for granted.
SQL is declarative. You tell SQL your intention:
How to best implement this? The nice thing is that you can mostly let SQL figure this out, merely giving him indications that you will use often this index to do searches.
Imperative programming is micro-management: do this, then do that, then do this, then do that.
If
Then ORMs are "Imperative"?
Nope, ORM are just a convenience wrapper to make SQL easier to use in your programming language, but apart from them pretty much the same.
If you were to create your own logic on how to fetch efficiently all users living in Berlin, that would be imperative.