July 4, 2026
SQL mates before shortcuts
What ORMs have taught me: just learn SQL (2014)
Programmers are dumping the ‘easy button’ and yelling: just learn the database stuff
TLDR: The writer says database helper tools often cause more trouble than they save, so learning plain SQL is the smarter move. In the comments, people turned that into a bigger fight about shortcuts, with jokes, nostalgia, and a mini-revolt over whether developers should learn fundamentals at all.
An old blog post about software shortcuts is suddenly serving fresh comment-section chaos. The writer’s big confession is simple: tools that promise to hide database work often create even bigger messes, especially once projects get large, slow, and full of weird business rules. In plain English, the supposed “easy mode” can turn into a maze, and the author’s conclusion is blunt: if you still need to understand the database anyway, just learn SQL — the language used to talk to databases directly.
But the real fireworks are in the replies. One camp treated the post like a timeless truth bomb. The funniest slam came from a commenter who basically said the story of tech is people getting mad they still have to learn things: in 2014 it was SQL, and by 2026 it’s anything at all. Another fan-favorite joke turned the whole database wars saga into a rom-com punchline: “NoSQL taught me to love SQL.” Ouch.
Still, not everyone was ready to throw the shortcut tools in the trash. One commenter argued that writing raw database commands can be annoying because editors often don’t catch mistakes well, so middle-ground tools can still help. Another swooped in with a nerdy-but-spicy correction, noting that one old recommendation in the article has aged badly because newer database features replaced it. And then, because the internet can never resist going further, one chaos agent suggested skipping SQL too and diving straight into even lower-level systems. Classic comments: half debate club, half stand-up set.
Key Points
- •The author concludes that ORMs should augment SQL rather than replace it.
- •The article is based on roughly 30 months of experience working with PostgreSQL and SQLite through SQLAlchemy and Hibernate.
- •It identifies practical ORM issues including partial objects, attribute creep, foreign-key-driven joins, and data retrieval inefficiency.
- •The author reports that adding explicit projections to ORM queries reduced some runtimes from minutes to seconds.
- •The article says complex or performance-sensitive querying often works better with direct SQL, including features such as window functions.