ERROR: permission denied for "GIRLS"
this post was submitted on 01 Jul 2024
298 points (91.6% liked)
LinkedinLunatics
3026 readers
120 users here now
A place to post ridiculous posts from linkedIn.com
(Full transparency.. a mod for this sub happens to work there.. but that doesn't influence his moderation or laughter at a lot of posts.)
founded 1 year ago
MODERATORS
~~and smallwaist = true~~
and itty_bitty_waist = true
and round_thing_in_your_face = true
is_sprung = true
It should be waist_size=1
I would reject this pull request. Why is the indenting all over the place? Why is your keyword capitalisation all over the place? WHY YELLOW?!
Edit: the more I look at this the more it pisses me off. Wtf is going on with your kerning? Just random number and placement of spaces. Also, why is the table name in caps? Who does that? Select * is lazy. Do you really need every field about a girl? Really? Worst of all, not a limited request. I sware this is just the kind of thing that would return 30 million rows and brick the database for twenty seconds.
You are now a Certified Rejector. Stay sharp, keep the wheel rolling.
You forgot some: Why is there no space after SELECT?
Why are boyfriend and smallwaist not questions like is_cute and is_crazy? Either all boils are with a verb or none.
Also why is smallwaist not in snake case? It should be small_waist (or better yet has_small_waist or even better waist = "small")
Also also boyfriend should be null not false, this would solve multiple issues.
And finally the only positive thing is the * itself, because selecting only body would be even worse. 🤣
load more comments
(5 replies)
This is not funny and any man wearing this would probably not pass a similar test using any woman's criteria. If I saw someone wearing this my first thought would certainly not be "hey this is a guy with a great sense of humor and I would like to hang with him!".
Should be age > (my_age / 2) +7
Found the programmer thread that criticises the data model instead of the t-shirt
Why would there be an age and my_age column on the table GIRLS?
Good point.
Should be
age > (@my_age / 2) +7
FTFOP - now my age is some value defined outside the immediate query.
More likely, the GIRLS would be a view of some table persons and you could query my_age from that table too.
load more comments
(3 replies)
most infurating part of this is the mixing of cases
At least he's wearing the red flag on the outside.
Guy with a belly asks for girl with a small waist. The half-assed ugly shirt will do it.
Instant woman repellant.
I feel confident in assuming the guy who would wear this shirt seeking “girls” between the ages of 18 and 26 is himself no younger than 45.
Ah I missed the age gap.
Would this guy qualify as an OUTER JOIN? (Sorry, SQL is not my native language)
I sure wouldn't want him as an INNER JOIN
yesss I'm 42 so I can wear this shirt with pride!
load more comments
(1 replies)
One of the reasons women will find this repugnant is because they didn't normalize their tables. Should be boyfriend_id is null.
For that matter, why is waist size a Boolean?
They allowed business logic to pollute the DB table, and "small waist" is a defined range in some confluence doc somewhere.
load more comments
(2 replies)
And why is cuteness and craziness binary?
load more comments
(1 replies)
Why is there a separate table for men and women in the first place? Shouldn't there be a person table with a many to many relationship with itself (because polyamory exists)?
To that point a person table with a relationship table. So this way you can reference relationship between two or more persons within the relationship table and that could be joined to the person table if needed. I don't think you'd really be able to keep it within one table while exploring multiple relationships unless you're storing a list of ids that is interpreted outside of sql. Also a relationship table would allow exploring other types of relationships such as exes, love interests, coworkers, family, friends, etc
load more comments
(2 replies)
load more comments
(1 replies)
Maybe it's supposed to imply that boyfriend is an attribute of the particular girl. Like saying she isn't someone's boyfriend. It's probably a holdover from the original data architecture and nobody ever bothered to modify the table later on in case there's a select somewhere that expects that field to exist.
Or, if you allow for polyamory and non-hetero relationships, you probably need a rel table (and some joins in the query).
Maybe GIRLS is just a view...
load more comments
(4 replies)
Gonna sound racist but deal with it.
I constantly meet asian developers (Singapore , India, China, etc) with this edgelord personality. They come to American conferences and meetups, say some wild sexist shit, and someone has to politely let them know not to.
Some backtrack. Some apologize. Some literally freeze up and pretend like it didn't happen.
We do still live in a bubble in the west. We're fighting for equity across genders and race, while some parts of the world are still questioning if sexual harassment against women at work is really that big of a deal.
Many of my guy coworkers have been (and are) sort of misogynistic, and homophobic (I'm in India). It makes me really uncomfortable. Might start reporting people to HR one day.
Just get to know HR first. They might be mysogynists themselves (even if they are female).
load more comments
(1 replies)
This is the most Indian shit I have seen this week.
I can already imagine a 40-something year old manager coming into work wearing this
This is why we have codes of conduct.
Who says programmers don't have a sense of humor?
No one. It's just what you pretend people say to make yourself feel like some kind of special exception.
load more comments
(2 replies)
shitty taste <> "humor"
Big pp energy over here
He forgot the "TOP 2" qualifier.
Heh. That reminds me of the feeling when I carefully place a LIMIT 100 and get 0 results...
Most SQL Dbs use bits, so it would be WHERE field = 1
The entire shirt caused me 4d6 psychological damage.
load more comments
(6 replies)
view more: next ›