Menu

Two people, one holiday: why you can't just average their preferences
πŸ“°

Two people, one holiday: why you can't just average their preferences

DEV Community: typescriptΒ·Sarthak AggarwalΒ·20 days ago
#evMrfEtC
#devtotypescript#devto#dev#score#destination
Reading 0:00
15s threshold

Two people. One holiday. Each has their own idea of a good time, and only one booking gets made.

I ran into this building honeymoon.wiki , a free reference for honeymoon destinations with a matchmaker for couples. Each partner answers separately, often on their own phone, and the app has to produce one shortlist they're both happy with.

The naive solution is obvious and wrong, so here's what actually works.

Why averaging fails

Score each destination for each partner, average the two, sort descending. Done in one line.

Then you look at the output and it's useless.

Say A wants a quiet island and B wants a city with nightlife. A place that scores 1.0 for A and 0.2 for B averages 0.6. A place that scores 0.62 for both also averages 0.6. The mean treats these as equivalent. They are not remotely equivalent: the first one means one person spends their honeymoon somewhere they actively didn't want.

Averaging optimises the couple as a single blended entity.…

Continue reading β€” create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.