Exactly! Devs should learn SQL and should learn how their ORM works, what it is doing "behind the scenes". It is also a good idea to keep a sql profiler open w

Exactly! Devs should learn SQL and should learn how their ORM works, what it is doing "behind the scenes". It is also a good idea to keep a sql profiler open when working with the application to see which queries are generated. When you do that regularly, you can often fix issues before they really become a problem. This is also useful even if you do not use an ORM. For example, an action might execute a loop with a query on the inside of the loop. It might be more performant to retrieve the data using one query and then loop over the results of that query.