Things I learned after getting users
&quot;this is mostly because i relied on a SQL ORM which in short is a tool that makes writing SQL easier to pick up and faster to develop. the biggest downside is that it might execute 50 queries to your database to get a list of information, when it probably only needs 1, which will cause slowdown.&quot;<p>I appreciate this honesty. Listen to this old man&#x27;s advise: learn SQL properly. It&#x27;s not that hard. Focus on it for a few weeks intensely and you&#x27;ve mastered it for life. Then just write SQL directly.<p>I&#x27;ve had weekends ruined troubleshooting my &quot;highly productive ORM layer&quot; that nuked a production database. Whilst functionally speaking my ORM code was in no way incorrect. I&#x27;m talking differences of a thousand fold in query load depending on how one expresses the ORM calls.<p>You can then become proficient in trying to reason and predict about what your ORM calls do in the actual database, but when you&#x27;re several joins deep, this becomes near impossible. At which point you become the ORM, and might as well just write SQL.