this post was submitted on 12 Apr 2025
49 points (100.0% liked)

Programming Circlejerk

157 readers
14 users here now

Community to talk about enlightened programming takes

Rules:

founded 2 months ago
MODERATORS
top 21 comments
sorted by: hot top controversial new old
[–] [email protected] 1 points 6 days ago

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

[–] [email protected] 29 points 1 week ago (1 children)

This guy is vibe coding his queries. That's the future of programming :(

[–] [email protected] 3 points 1 week ago (1 children)

God I hate that term. They just put vibe in front of it and act like copy/pasting things you don't understand is "coding."

[–] [email protected] 8 points 1 week ago (2 children)

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.

[–] [email protected] 1 points 1 week ago

I love to hate this

[–] [email protected] 1 points 1 week ago

vibe rator?

[–] [email protected] 24 points 1 week ago

Somebody needs to learn to design his database layout by common queries and performance standards.

[–] [email protected] 21 points 1 week ago

Y’all must be running Oracle DB if your SQL is not scaling.

[–] [email protected] 17 points 1 week ago (1 children)

😅 what year is this guy living in? SQL has scaled, probably better than any other software paradigm.

[–] Kichae 12 points 1 week ago (1 children)

Yes, but if I do 80 joins and don't specify join conditions, things get, like, super slow, Scoobs!

[–] [email protected] 1 points 1 week ago

That's why you should only left outer inner right join with a recursive select!

[–] [email protected] 12 points 1 week ago (2 children)

Do we need to bring out the Mongo DB web scale video again?

[–] [email protected] 4 points 1 week ago (1 children)
[–] [email protected] 16 points 1 week ago (1 children)
[–] [email protected] 3 points 1 week ago

thanks for sharing this goldmine

[–] [email protected] 2 points 1 week ago

First thing I thought of when I read this, and if you click through to the actual Linkedin post, that's exactly what the twit is saying.

[–] [email protected] 7 points 1 week ago

Oh, he's on AWS, that might explain some things

[–] [email protected] 4 points 1 week ago

as someone who has never coded in SQL and only knows some python, SQL is so scalable it sheds every 3 weeks

[–] [email protected] 2 points 1 week ago* (last edited 1 week ago) (2 children)

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.

[–] [email protected] 2 points 5 days ago* (last edited 5 days ago)

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.

[–] [email protected] 2 points 6 days ago

But that's work! How dare you ask me to do work!