Earlier quoted context omitted.
That’s essentially a cliché false dichotomy. Wouldn’t it be even nicer to work with someone who can express how they feel in a constructive and helpful manner?
Imagine you are Linux and you receive a messy patch so poorly structured that you can't follow the logic of the code. As Tony Hoare used to put it, the kind of code that doesn't have obvious bugs, but isn't obviously free of bugs. What do you tell the submitter? You can't really point at specific problems, merely at a gut feeling that the mess must be hiding problems. Then the submitter shoots back: "You rejected my…
If the code is too clever for you, ask them to refactor in a simpler way rather than rejecting outright.