The problem is that a reasonable context response is different from person to person and culture to culture. I feel like this makes things like using operator

The problem is that a reasonable context response is different from person to person and culture to culture. I feel like this makes things like using operator overloading to clean up code incredibly dangerous, especially in popular libraries. Best: Context-appropriate overload that makes sense to me Good: Standard language meaning that may not fit cleanly in context, but has the same definition always Worst: Context-appropriate overload that doesn't make sense to me So if you aren't sure whether or not your clever idea will actually fall in the third category for some people, go with the second instead of pushing for the first. Aka, "for every story someone can tell of a magical operator overloading that makes code more readable, I can come up with some dumbass architect who did the most counterintuitive thing you can imagine."