The Only Database Abstraction You Need
You are interacting with databases wrong. You shouldn't use ORMs even though they are the default for many instead of SQL. ORMs are bad and constrict you unnecessarily. You should prefer to use SQL and after this video you will. By using SQL you will supercharge the usability of your database. Although there are nice areas to use ORMs - like database migrations. Also, sorry about my voice, I was a bit sick during recording :(
▶︎
How much database abstraction do I need? - Alexander M. Turek
▶︎
MIT Professor on Data Abstraction & Object-Oriented Programming
▶︎
I’ve been using SQL wrong this whole time
▶︎
DONT USE AN ORM | Prime Reacts
▶︎
How Agents Quietly Break Architecture
▶︎
Learn Database Normalization - 1NF, 2NF, 3NF, 4NF, 5NF
▶︎
Why AI Has Failed to Take Your Job Since 1976
▶︎
Postgres can replace your entire stack...
▶︎
Why Can't We Make Simple Software? - Peter van Hardenberg
▶︎
Postgres is NOT A DATABASE.
▶︎
What Is Abstraction in Computer Science
▶︎
you need to learn SQL RIGHT NOW!! (SQL Tutorial for Beginners)
▶︎
Learn Database Denormalization
▶︎
Turing Award Winner: Disagreeing with Google, Postgres, Future Problems | Mike Stonebraker
▶︎
The Biggest Database Design Mistake
▶︎
The Stockholm Syndrome of SQL | Prime Reacts
▶︎
The Moment That Changed Software Development!
▶︎
Co-Creator of Haskell: Functional Programming, Thinking in Types, Useless Languages | Simon Jones
▶︎
I've been using Redis wrong this whole time...
▶︎