this post was submitted on 15 Jul 2023
1214 points (98.9% liked)

Programmer Humor

19623 readers
25 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 1 year ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] snowe@programming.dev 12 points 1 year ago (1 children)

Imports wouldn’t help. It’s setters with a ton of chained getters

[–] hughperman@sh.itjust.works 6 points 1 year ago (2 children)

Mostly they're all the same up to the last one or two methods - just set the common part as a variable?

[–] snowe@programming.dev 3 points 1 year ago (1 children)

Definitely. I’m pretty sure they modified the code to look as bad as possible just to take the photo though. You can clearly see all the lines are marked as modified in the gutter.

[–] hughperman@sh.itjust.works 3 points 1 year ago

It's also a good way to potentially multiply your query costs and slow down the function, while introducing possible inconsistencies if the objects are modified between the first and last time they are requested.

[–] clutchmatic@lemmy.world 1 points 1 year ago

This is the best answer.... Or the outer classes being delegated access to the inner ones and so on, like an onion.

I wonder if this is one of the situations that Kotlin delegated parameters were designed to handle? (I'm new to Kotlin and still don't understand that "by" construct there)