I've run into this when working with lambdas in particular. Say for instance I want to track the performance of a particular bit of code in a standardized way. I can write a method that takes a supplier and handles the performance tracking while calling the supplier and returning the result. This way tracked functions don't have a load of eg. timer initialization etc. If the supplier throws a checked exception, it should be caught and handled by the code that actually cares about the call, not the performance wrapper.
Unfortunately, because of the way Java handles checked exceptions, I can't feed the supplier with a lambda or any other method reference that I'm aware of that throws a checked exception and let it be passed up to the original caller directly. So I need to catch my checked exceptions and wrap them in an unchecked exception to catch. Not pretty.
There's probably something I'm missing but the language certainly doesn't go out of its way to help with this sort of thing.
If my experience in retail is any indicator you're lucky if that request gets approved....and even luckier if your manager remembers that they approved your request!
I agree with this sentiment and would like to see more this sort of this not just for moderators but for every "low skill" job. Especially the C-level employees and shareholders - no one should be asking anyone to do something without either A) doing it themselves so they know what they're asking or B) treating the workers as experts whose opinions and requests should be taken seriously.
The fact that you and parent are getting downvoted just shows how out of touch with reality some developers have become. They really are exhibiting the same cluelessness they often attribute to managers.
There’s more. I think people are afraid. First from having to do something “unpleasant” and on a deeper level from loosing their own status of “importance”. It’s a pity indeed.
I answered "both" because I'm not running all of the projects I'm working on and some of them prefer tabs and others spaces - so I just go with the convention that that particular project uses.
+1 - Another great example of difficult games as parody is I Wanna Be The Guy (https://en.wikipedia.org/wiki/I_Wanna_Be_the_Guy). Take all the existing conventions and stereotypes of difficult platform games and exaggerate them to the extreme.
IWBTG is another great example, definitely. And almost the exact same type of classic-NES parody, where Mario:Syobon::Metroid:IWBTG.
Thinking about it a little more, this pattern seems to describe an entire class of games, including non-parodies. Dark Souls is famously hard because of sheer mechanical difficulty, certainly. But it's also rife with learnable, low-threat moments like "when you walk up this staircase, a boulder will fall on you from offscreen". They don't alter the overall difficulty too much, but they clearly convey that the game isn't honoring standard design principles about giving the player a "fair chance". In an odd way, it makes later departures like "the illusory wall doesn't have anything marking its location" feel more justified.
This was deliberate on Douglas Adams' part [0]. It's all part of the joke. Other notable sections are where the game actively lies to you about being able to access a particular room (you need to try to enter several times in a row), and then sulks when you call it out and lies about the contents of the room.
Yep - a lot of text adventures were brutally hard, often to make up length, but the Hitchhiker's Guide game was something else altogether. It was tricky, but also gratuitously unfair for the sake of comedy. A lot of it doubled as parody of earlier text adventures, like recreating "guess the command" difficulties by forcing the player to "take buffered analgesic" instead of "take aspirin".
The most famous example, I think, is the babel fish machine: it wasn't actually hard, in the sense that each failure told you exactly what you needed to do fix. But it was unfair, because you got one fewer attempt than the number of steps required. The designers basically expected you would roll your eyes, laugh, and try again with that extra knowledge.
(Which is a pretty standard part of punishingly hard games even today, interestingly. Dark Souls is mechanically hard, but it's also full of easily-managed surprises that are mostly present to create a feeling that the implicit rules of fair design aren't in effect.)
To add onto your comment - I'd also consider a work environment that automatically assigns the documentation, test-writing, etc. to a gender minority (or other minority) to be toxic.
Unfortunately, because of the way Java handles checked exceptions, I can't feed the supplier with a lambda or any other method reference that I'm aware of that throws a checked exception and let it be passed up to the original caller directly. So I need to catch my checked exceptions and wrap them in an unchecked exception to catch. Not pretty.
There's probably something I'm missing but the language certainly doesn't go out of its way to help with this sort of thing.