Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add "other" field to selection questions #14

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

fricklerhandwerk
Copy link
Contributor

there was a lot of feedback where people couldn't submit their outlier data, and a major value of the survey is to give people an opportunity to get heard

there was a lot of feedback where people couldn't submit their outlier data, and a major value of the survey is to give people an opportunity to get heard
@GuillaumeDesforges
Copy link
Owner

GuillaumeDesforges commented Nov 11, 2024

Copy of my thoughts from the previous PR:

I'm strongly against it. It circles back to open-ended questions being costly and hard to analyze.

IMO one of the reasons we could make the most of the survey in 2024 was that we put more thought in the question prompt and answer choices. If anything is missing, it should be added to everybody.
A very probable risk I foresee is that many people will prefer using the "other" choice to input a choice that would usually fall into one of the provided category. While I agree that it is important to be open and inclusive, I think it is our responsibility to provide usable data as well. Basically, if people feel a question needed an "Other" field, we need to work on the question instead, e.g. provide more choices or clarify the prompt of the question.

But in the end, whoever implements the survey is free to do what they want, so I'll let the PR open until next survey is designed.

@fricklerhandwerk
Copy link
Contributor Author

fricklerhandwerk commented Nov 11, 2024

Providing more choices is not always an option. People rightfully complained about questions that had dozens of options were confusing, and finding all the possible enum answers is an uphill battle. Do you really want to list 50 languages people could be working with? Most of them will be hyper niche

@GuillaumeDesforges
Copy link
Owner

Fair point. Then the question is "which questions should have an 'Other' choice?" which I find much more reasonable.

@GuillaumeDesforges
Copy link
Owner

Also, is it an 'Others' choice with a free text input or without?

@fricklerhandwerk
Copy link
Contributor Author

I suggest that all single and multi select questions that have an unbounded domain should have a freeform "other" field.

Example: Which languages do you program in?

Counter-example: Which Nix experimental features do you use?

The rule of thumb should be to have a fixed number of most-often selected answers from past years be hard coded and leave the tail end open. We can throw ML at the rest to do a clustering, and whatever is left is almost always a curious outlier worth an honorable mention.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants