I could imagine that one of the ways for the fallout not to be disastrously traumatic is if one accepts whatever “judgement” is to come ie guanteed pleadingly quilty with no/little resistance. Say that pushing people into pool unhappily means you get side-eyed for 30 minutes. If one knows the fallout beforehand there is no chance of an undefinite downward spiral. The way that a traumatic fallout occurs if the people disagree on how to proceed (ie no punishment vs punishment).
I am kind of linking this in my mind to the “try catch” programming pattern. Some might have a style preference that correctly working code should not deal with errors too much (ie representing “not found” as “return −1” or “raise NoSuchElementException”). I tried to search for previous usage of that that and indeed The Magnitude of His Own Folly is structured as a story about how a exception that was caught in a bad way was made uncaught and allowed to escalate. Curious that also explictly deals with trust.
In a problematic situation a party might have no choice but to trust. In a hostile work environment you can have the choice of working or not working. Deducing from peope choosing work (and thus “implicit trust”) that there is a good environment is not the most reliable of logics. Assholes can be “recklessly clueless” and that counts against them rather than for them.
Yeah, trusting the overall system of punishment/consequence to be at least approximately fair, and that everyone involved has enough spare resources to survive/absorb occasional small miscarriages of justice, is a crucial part of this.
I could imagine that one of the ways for the fallout not to be disastrously traumatic is if one accepts whatever “judgement” is to come ie guanteed pleadingly quilty with no/little resistance. Say that pushing people into pool unhappily means you get side-eyed for 30 minutes. If one knows the fallout beforehand there is no chance of an undefinite downward spiral. The way that a traumatic fallout occurs if the people disagree on how to proceed (ie no punishment vs punishment).
I am kind of linking this in my mind to the “try catch” programming pattern. Some might have a style preference that correctly working code should not deal with errors too much (ie representing “not found” as “return −1” or “raise NoSuchElementException”). I tried to search for previous usage of that that and indeed The Magnitude of His Own Folly is structured as a story about how a exception that was caught in a bad way was made uncaught and allowed to escalate. Curious that also explictly deals with trust.
In a problematic situation a party might have no choice but to trust. In a hostile work environment you can have the choice of working or not working. Deducing from peope choosing work (and thus “implicit trust”) that there is a good environment is not the most reliable of logics. Assholes can be “recklessly clueless” and that counts against them rather than for them.
Yeah, trusting the overall system of punishment/consequence to be at least approximately fair, and that everyone involved has enough spare resources to survive/absorb occasional small miscarriages of justice, is a crucial part of this.