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.
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!
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?
And why is cuteness and craziness binary?
They allowed business logic to pollute the DB table, and “small waist” is a defined range in some confluence doc somewhere.
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)?
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!”.
At least he’s wearing the red flag on the outside.
