AI
AWS
Agile
Algorithms
Android
Apple
Backend
Bash
C++
Cloud
Csharp
So you're building your app and you're like "I'll use an ORM for database abstraction so I can switch databases later!" Sure, Jan. Sure you will.
The brutal truth? Both the galaxy-brain geniuses writing raw SQL and the smooth-brain rebels who also write raw SQL have figured out what the ORM evangelists refuse to admit: you're NEVER switching databases. That Postgres instance you spun up on day one? That's your ride-or-die until the heat death of the universe.
Meanwhile, the "average" developers are stuck in the middle with their ORMs, adding layers of abstraction for a migration that'll never happen, debugging cryptic ORM-generated queries, and pretending they're writing "portable" code. Spoiler alert: the only thing you're porting is technical debt.
The real power move? Just admit you're married to your database and write those beautiful, optimized raw queries without shame. Your future self will thank you when you're not deciphering what monstrosity your ORM generated at 3 AM.
