Comment on Malicious compliance
Feathercrown@lemmy.world 5 days agoErm ackshually that’s not really a valid application of hanlon’s razor because the entities being referred to as stupid or malicious are two separate beings
Comment on Malicious compliance
Feathercrown@lemmy.world 5 days agoErm ackshually that’s not really a valid application of hanlon’s razor because the entities being referred to as stupid or malicious are two separate beings
Sumocat@lemmy.world 5 days ago
That’s not a requirement of Hanlon’s razor. Stupidity can be introduced at any point in the process. If a commander orders a firing squad to form a circle and they shoot each other, that’s on the commander, not the squad for shooting each other.
Feathercrown@lemmy.world 5 days ago
But in that scenario the subject of interest (who we’re trying to determine if they’re stupid or malicious) is the commander regardless of whether they were stupid or they were malicious. In your original scenario, you aren’t comparing the hypothesis of a malicious employee to a stupid employee, you’re comparing a malicious employee to stupid instructions. Hanlon’s razor does not imply the employee is not malicious because you aren’t using it to imply the employee is stupid, you’re claiming the instructions are stupid, which is a perfectly good motivation for malicious behavior from the employee. A correct usage of Hanlon’s Razor here would be to say that you should assume the employees are stupid rather than malicious. I disagree with that interpretation because Hanlon’s Razor is often wrong, but it’s at least a valid usage of it.