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
Let students rate the difficulty of an exercise #4229
Comments
Hello 👋 With the launch of Exercism v3, we are closing all issues in this repository to help give us a clean slate to detect new problems. If this issue is still relevant to Exercism v3 (e.g. it's a feature that we haven't implemented in v3, or a bug that still exists), please reopen it and we will review it and post an update on it as soon as we get chance. Thanks for helping make Exercism better, and we hope you enjoy v3 🙂 |
AFAICT this is still relevant and should be reopened. |
One thing that wouldn't necessarily give good results quickly, but could provide a good aggregate over time is to ask them to compare the exercise to the one they completed right before it: easier, same-ish, harder. |
Might not be great for difficulty, but would be pretty nice for tracking "difficulty to progress" |
All exercises are assigned a difficulty 1-10 by the track maintainers and contributors and this is displayed on the website.
I recently asked on Slack how other maintainers determine the difficulty and most responses came down to guessing/estimating based on how difficulty they found it themselves and then adjusting it if someone complains later on. Further, some responses noted more objective criterias would be nice or that they tried to crowdsource the difficulty in the past but didn't get enough responses.
It might be helpful to determine more meaningful difficulty ratings if students could rate the difficulty of an exercise after solving it and maintainers/mentors could see the average rating somewhere. This should not be used as the public difficulty rating but just as a reference.
What do you think?
The text was updated successfully, but these errors were encountered: