▲ 1230 ▼ finally there is a perfect monitor for Java programmers (lemmy.ml) submitted 3 years ago by likeaduck@programming.dev to c/programmer_humor@programming.dev 116 comments fedilink hide all child comments
[–] clutchmatic@lemmy.world 8 points 3 years ago (5 children) ...and that, kids, is why java has this thing called imports permalink fedilink source hideshow 5 child comments replies: [–] snowe@programming.dev 12 points 3 years ago (4 children) Imports wouldn’t help. It’s setters with a ton of chained getters permalink fedilink source parent hideshow 4 child comments replies: [–] hughperman@sh.itjust.works 6 points 3 years ago (3 children) Mostly they're all the same up to the last one or two methods - just set the common part as a variable? permalink fedilink source parent hideshow 3 child comments replies: [–] snowe@programming.dev 3 points 3 years ago (1 child) 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. permalink fedilink source parent hideshow 1 child comment replies: [–] hughperman@sh.itjust.works 3 points 3 years 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. permalink fedilink source parent [–] clutchmatic@lemmy.world 1 point 3 years 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) permalink fedilink source parent
[–] snowe@programming.dev 12 points 3 years ago (4 children) Imports wouldn’t help. It’s setters with a ton of chained getters permalink fedilink source parent hideshow 4 child comments replies: [–] hughperman@sh.itjust.works 6 points 3 years ago (3 children) Mostly they're all the same up to the last one or two methods - just set the common part as a variable? permalink fedilink source parent hideshow 3 child comments replies: [–] snowe@programming.dev 3 points 3 years ago (1 child) 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. permalink fedilink source parent hideshow 1 child comment replies: [–] hughperman@sh.itjust.works 3 points 3 years 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. permalink fedilink source parent [–] clutchmatic@lemmy.world 1 point 3 years 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) permalink fedilink source parent
[–] hughperman@sh.itjust.works 6 points 3 years ago (3 children) Mostly they're all the same up to the last one or two methods - just set the common part as a variable? permalink fedilink source parent hideshow 3 child comments replies: [–] snowe@programming.dev 3 points 3 years ago (1 child) 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. permalink fedilink source parent hideshow 1 child comment replies: [–] hughperman@sh.itjust.works 3 points 3 years 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. permalink fedilink source parent [–] clutchmatic@lemmy.world 1 point 3 years 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) permalink fedilink source parent
[–] snowe@programming.dev 3 points 3 years ago (1 child) 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. permalink fedilink source parent hideshow 1 child comment replies: [–] hughperman@sh.itjust.works 3 points 3 years 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. permalink fedilink source parent
[–] hughperman@sh.itjust.works 3 points 3 years 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. permalink fedilink source parent
[–] clutchmatic@lemmy.world 1 point 3 years 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) permalink fedilink source parent