Software that is designed correctly separates out what it does, how it does it, and how it interacts with the outside world.
Ergo, software that is correctly designed is user-agnostic. If the user thinks in a particular way, whatever that way happens to be, it is the job of the software to accommodate that. If it does not, it is not software for users, it is software that has users. Possession is everything.
Software that is correctly designed is configuration-agnostic. If the configuration file states something is enabled, then that is enabled. It is not the job of the software to say the file really means something else. If the configuration is broken, state how and why. Clearly. If the configuration is old, import and update. But don't tell me, or anyone else, what Joe Bloggs thinks would look better. I don't care. And the more other people's preferences get shoved in my face, the less I will care.
Theo clearly has the right idea - the only way to get past the morons is with an attitude of utter contempt. Bugger all else matters, apparently.