People often say SQL has no problem to scale but they've never actually done it
2 years ago by Drew to c/programmingcirclejerk
I think it is a perfect term. It so accurately describes how terrible the outcome must be. You can use it with other high-skilled jobs as well: vibe surgery, vibe piloting, vibe architecture.
vibe rator?
What is it about?
as someone who has never coded in SQL and only knows some python, SQL is so scalable it sheds every 3 weeks
How about adding indexes and stats on the appropriate columns, and have look at your execution plan while you're complaining. Bushels of low hanging fruit are ready to be picked for devs who bother with a little SQL performance tuning.
But that's work! How dare you ask me to do work!
And if doing pagination, order by an index and add a minimum bound, instead of doing LIMIT 5000,5000.
Oh and if the query optimizer picks a bad index for what you're doing, you can force a better one.
And don't do dependent subqueries and...
Idk, this is stuff I learned in my first year or 2 at my first job in the field. And I've had people on reddit tell me I'm a programmer not a software engineer because I don't have the education so therefore I can only be a code monkey. Yet somehow Amazon pays people 5x my salary to not know how to use SQL efficiently while I'm out here building queries that show no non-index reads, sometimes in databases where I'm not even allowed to add new indexes because of legacy reasons.
So there was this QA tester filling a million documents in the database (NOSQL) and then using a single fetch to get all the data without pagination and then telling me my library was first being slow and then crashing.
Of course I didn't handle std::bad_alloc
@programming.dev
Community to talk about enlightened programming takes
Rules:
go to feed...
@programming.dev
Community to talk about enlightened programming takes
Rules:
go to feed...
This guy is vibe coding his queries. That's the future of programming :(
save