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.
I would like to subscribe to your newsletter.
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. 🤣
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.
yesss I’m 42 so I can wear this shirt with pride!
And married.
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.
And why is cuteness and craziness binary?
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
Are you really doing relational data if it has nulls though?
I can already imagine a 40-something year old manager coming into work wearing this
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!”.
ERROR: permission denied for “GIRLS”
This is why we have codes of conduct.
and smallwaist = trueand itty_bitty_waist = true
and round_thing_in_your_face = true
It should be waist_size=1
is_sprung = true
Should be
age > (my_age / 2) +7
This is the most Indian shit I have seen this week.
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.
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).
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.
That last part is a face saving culture reaction. If you’re feeling culturally sensitive the thing to do is just move on and see if they do it again.
shitty taste <> “humor”
That is really a shirt for SQL enthusiast. Now, I want to rebuild the database and write some convention for writing request.
The pallette for the syntax highlighter is horrid. Hardly readable.