I have been on both the receiving and producing end of a similar decision making process whereby all stakeholders are consulted, and then a solution is provided which has as its only real design consideration - beyond being effective - that no-one gets exactly what they requested.

Is there a name for this kind of anti-consensus decision making?

Not sure if there’s a name for this, but my favourite example is settling on UTC as the acronym for Coordinated Universal Time:

https://en.m.wikipedia.org/wiki/Coordinated_Universal_Time#E...

ISO stands for the International Organization for Standardization, for largely the same reasons.

Maybe I got the wrong person (on the phone), but it was explained to me the name "ISO" was the Greek word for "sameness" and that Français and English just happened to form /meaningful/ representations for an acronym.

"IT'S ALL IN THE NAME Because 'International Organization for Standardization' would have different acronyms in different languages (IOS in English, OIN in French for Organisation internationale de normalisation), our founders decided to give it the short form ISO. ISO is derived from the Greek isos, meaning equal. Whatever the country, whatever the language, we are always ISO." https://www.iso.org/about-us.html

But I'd tend to call BS - if it wasn't ever an acronym, why capitalize all three letters?

The google ngrams are also suggestive:

https://books.google.com/ngrams/graph?content=international+...

The Greek ισο "iso" does mean "equal". I do not know if that influenced the naming of the organization, though.

You see this word in many English roots, such as isotropic, isometric, isomer, etc.

In a similar vein, the acronym for Web Ontology Language is OWL[1].

[1]: https://www.w3.org/OWL/

Great question! I wish I knew!

It’s a weird scenario as people are very emotional about their chosen position during the discussion, but literally nobody gives a hoot once a decision was made.

In our case, multiple organizations were merged, so the perception one camp “winning” was important to avoid.

I'd call that a compromise.

I like the sound of "anti-compromise."

Compromise?

No; the point here is to pick the worst possible compromise out of compromises that solve the problem effectively.

It's like you're dividing an 8-piece pizza between 3 people. Everyone's minimum desire is 2 pieces, compromise solution would be 2 and 2/3 split, and people keep arguing why they deserve more. However you - the decision maker - decide instead to give everyone 2 pieces and throw the remaining 3 pieces into the bin, because shut up and get back to work.

You understand perfectly: everyone got enough food to keep going, and they are equally dissatisfied with the result. I might take a step to the left by ordering known-unpalatable toppings and provide no further allocation instructions, but the effect is the same.

If there are 3 people, and they each get 2 slices, that is 6 slices.

So, throwing away 2 slices, because there is 8 total, is fine, as you stated that is everybody’s agreed minimum desired amount.

And there is no knife, nor protractor.

What is the difference between the worst and best compromise? If it is a compromise, it is a compromise.

Anti-compromise: A solution which pleases the fewest parties possible while still meeting each party’s needs.

Compromise: A solution which pleases the most parties possible while still meeting each party’s needs.

I'm in Denmark, it has been my experience that the most common naming scheme (I would say omnipresent naming scheme almost) is to use the old Norse Pantheon for names.

Similar in Greek academic networks, adapting to local mythology. The amount of routers and mail servers named 'Hermes' was ridiculous.

Different experience in English academia, where I encountered random names (e.g. 'mira' for a shell server and 'laplace' for a Physics Dept server). The acronyms could at times be interesting. Particular favourite was a 'central university network time' server. That was later renamed to ntp.*.ac.uk, after stern recommendations.

Around 2000 I was working at the small bank that had servers named by currency. Development server happened to be "dong". Eudora had some spicy language detection and used to show me some red chili peppers every time I'd mention that server in email.

In Colorado, USA, all 5 companies I've been inside conference rooms of use specific mountains (or ski towns) in the area. I've been in meetings in Longs Peak in 3 different companies.

Same experience in Norway and Sweden. Followed very closely by sci-fi/fantasy characters or authors.

I've noticed the Pritunl VPN suite uses that to name nodes. Two words (adjective + noun) and a number.

> Naming standards are the ultimate bikeshedding event.

I hope you never write a single line of code with this mentality...