this post was submitted on 10 Jul 2024
658 points (99.0% liked)

Programmer Humor

19817 readers
60 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 2 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] Fades@lemmy.world 15 points 5 months ago (3 children)

Why are females typed differently than males instead of a base class human with a gender identity parameter? Why would human anything have a function called young?? What would that function even do????

[–] purplemonkeymad@programming.dev 4 points 5 months ago (1 children)

HumanFemales and HumanM both inherit from the Ape base class, it's from an older java code base. We tried to change it once but it turned out the person that had written had retired and any changes we made just broke stuff.

[–] Fades@lemmy.world 1 points 5 months ago

Haha, I like this answer!

[–] qarbone@lemmy.world 2 points 5 months ago

Could be a subclass. However, it should just be an 'is' method which is passed the array of [young, pretty] as input

[–] cheddar@programming.dev 2 points 5 months ago (1 children)

The young method returns a boolean parameter. Females have a different type for obvious biological discrepancies that require extra functionality.

[–] Fades@lemmy.world 1 points 5 months ago* (last edited 5 months ago)

I can accept your second point, but in your PR I would absolutely request you to rename the method to isYoung, and then in making said comment I would then ask… what value isYoung providing, and where is the line between young and !young ultimately for trying to get the dev to reevaluate the design. It’s hyper specific in an obtuse manner and I think it hints at design flaws especially with the perspective of product evolution