Is ORM still an anti-pattern?
A point I&#x27;m missing is: without using an ORM (or however else you&#x27;re calling your database interface) you will eventually end up writing <i>and maintaining</i> one yourself, at least for CRUD stuff, and it will be filled with weird bugs, edge cases and security holes.<p>&gt; A common complaint about ORMs is that they break two of the SOLID rules. If you aren’t familiar with SOLID, it is an acronym for the principles that are taught in college classes about software design.<p>And that right here is the problem. Academia is teaching people stuff that makes sense <i>in an academic environment</i> where time, maintainability, money and effort aren&#x27;t of a concern (as long as you have grant money, but that&#x27;s not relevant here) - and that leads to a <i>very</i> nasty collision when fresh graduates enter the workforce. They&#x27;re used to shaving yaks and reinvent wheels all day long in the quest for a &quot;perfect&quot; solution, and if the company doesn&#x27;t have (enough and qualified) senior&#x2F;lead developers to catch that, you end up with ... very interesting products, budget overruns and&#x2F;or dumpster fires. Or a combination of all of them.<p>ETA: There&#x27;s something that can go <i>even worse</i>: when stuff designed by and for academics enters public availability. The best&#x2F;worst example for that is OpenStack... enough knobs and twists to support the specialized environment of CERN and probably hundreds of universities worldwide, with components modularized to an <i>insane</i> degree, but almost impossible to get started with because it&#x27;s so byzantine.