You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 30, 2022. It is now read-only.
My gut is saying there are two types of no-match lists we need to make:
A no-match "already friends" list. These are people who already know each other, and the benefits of getting to know team members would be lost on these pairs.
A match-only-if-necessary list. These are people who have been previously matched, and so we should try to not match them first.
Thoughts?
The text was updated successfully, but these errors were encountered:
The "already friends" list feels v2 to me and the previous matches feels more important.
Other matches I've considered are:
These people work on a team together (this seems less necessary, because we might see value from people on the same team having personal conversations instead of just work)
These people both work in the Carlsbad office (this seems like it makes sense on some level, but also takes away from the level playing field we're trying to create)
I think keeping this as generic as possible is probably the best. Hopefully we can open source this puppy. So I think keeping it to just the "already friends" feature is probably good enough to solve most problems. If I don't want to match with people on my team, I just put them on my already friends list.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
My gut is saying there are two types of no-match lists we need to make:
Thoughts?
The text was updated successfully, but these errors were encountered: