3 ms·
And then you learn SQL, which you should, you'll know when using an ORM is the right option. You might even be able to evaluate them better. I suppose the sam
by wvenable 3y ago
And then you learn SQL, which you should, you'll know when using an ORM is the right option. You might even be able to evaluate them better.
I suppose the same with CSS -- knowing it means you'll have much more flexibility and understanding when picking a CSS library for convenience.
- systems_glitch 3y agoIndeed, my introduction to databases was extracting stuff using Perl's DBI and getting good at pushing the work out to the DB. When I was introduced to ORMs it was instantly clear that they were a game changer for MVC development. I've transitioned a few legacy (large) Rails applications through Arel and often did not understand why we were putting the work in, other than to make it easier on new/future developers who did not understand SQL. In pretty much all of them we ended up having to keep some non-Arel queries -- you know, the ones where `STRAIGHT_JOIN` cuts 5 minutes off a query!