Exercise Ordering
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
Research direction
Start by reviewing the current core exercise ordering and the exercise-ordering setup from #187, using the linked exercism-config-viz visualizer. Gather feedback from track mentors and current or recent students, and consider the requested removal of Gigasecond and Meetup in relation to #233. Done means agreeing on an updated ordering and completing the related manual website work noted in #262.
Written by the indexing model from the issue text.
Description
I'm not sure if the exercise ordering makes much sense. The core exercises and the exercise ordering was setup in #187, and they may need to be updated or changed. (I know of at least a couple changes I want to see happen, which I'll list here).
We're looking for someone to take on this task, figuring out if the ordering makes sense now after it's been active for several months, and possibly reordering many of the exercises. This would work best if we got feedback from the mentors for the track, and possibly from current or recent students.
I can help and provide input, but I may not have time to take this on myself. And I haven't mentored or done any exercises on exercism.io since they launched the new version of the website, so I don't personally have great context for what would make sense.
The one thing I want to happen is to make Gigasecond and Meetup not part of the core track to help with #233. I may end up making just that change myself if necessary, but the rest of the exercises need to be looked at as well.
This visualizer may help: https://github.com/jonmcalder/exercism-config-viz
Important Note: Any changes to the core exercises will need some manual work elsewhere to update the website. See #262 for an example.
- Dominant language
- C++
- Stars
- 291
- Forks
- 244
- Avg merge
- 17m
- Merged PRs (30d)
- 1
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from exercism/cpp
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
ros2/message_filters#338 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
subsurface/subsurface#4984 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
flutter-webrtc/flutter-webrtc#2206 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
google-ai-edge/LiteRT-LM#3739 ·