"Trust, but verify" is a semantically null expression that appears to have filtered out of the Soviet Union during arms reduction negotiations, and eagerly taken up by Reagan administration appointees.
In a modern context it means, look for errors but not deception. It's how I approach code review.
* Any Soviet saying would come from a culture used to double-speak to survive government oppression and censorship. Which is probably still new to many Americans who remember good old days.
It's been straight up surreal watching the world turn into the George Orwell "1984" world we were all warned about as children, and seeing the USA (Land of "Freedom") gleefully join in the dystopian "fun".
Either way, if you insist on an excessively narrow definition of trust as being "never verifying", then yes, they're mutually exclusive... but only because it's circular logic.
Bar tabs are a good example of this behavior. Just get your regular a drink and assume their card will go through. In the past checks worked like this too.
1. Let the person start doing what they set out to do.
2. Check if they actually have permission.
3a. If yes, stop.
3b. If no, block their access.I mean, when you get any. That is increasingly rare.
"How can it be both NEW and IMPROVED?"
is there some kind of equivalent of aphantasia but for the feeling of trusting something ?
I'm not racist, but <some racist shit>.
You don't like the Corvette. Not that Corvette. However, you like Corvettes in general. Or you only like red Corvettes.
> I like steak, but
Turn the comma into a period: I like steak. It's unconditional; steak is a big yes for you. Except it's not. You have conditions. So sometimes you like steak and sometimes the opposite. You don't like steak.
I think the interpretation of but is not as trivially stupid as you say.
You can only ever trust or verify. "Trust, but verify" is functionally identical to "verify", thus, equivalently, "distrust, therefore verify", with maybe a generous helping of cynicism, doublethink, and official mollification.