-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Copy Ruby Track's core progression #1633
Conversation
- Copy Ruby's core exercise progression as a first step to help decrease the mentoring workload.
As Leap is not core anymore, the dependent side exercises need to be unlocked by something else. The choice is quite arbitrary.
Un-core, same as in Ruby.
Un-core, same as in Ruby: In Ruby we don't want bitwise operation exercises in core.
Un-core, because it's a math exercise
We don't have it (yet!) in the Ruby track, but I saw no reason why it couldn't be a core. I put it between somewhere midway.
Same as with Kindergarten: not a core in Ruby, but no obvious reason that it makes it unfit as a core exercise.
Make Saddle Points a side, because it's too similar to Matrix to have them both as a core.
Same as we did in Ruby: we made topics with CS and/or Data Structures a topic for side exercises.
.. because we want that in Ruby too ;-) But, because it's hard in Ruby, I moved it to the end of the track.
We're probably going to add it to the Ruby track as a core too.
Yes or no? Not quite sure. I'd expect it's better as a side exercise, but I had no good reason so I kept it for now, nearly to the end of the track.
There's a gap in the intermediate exercises, where in Ruby we have exercises that Python doesn't have. So, I promoted a few exercises that are on that same level in Ruby.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've found this helpful when making major changes to config.json
: https://jonmcalder.shinyapps.io/exercism-config-viz/
config.json
Outdated
"uuid": "7961c852-c87a-44b0-b152-efea3ac8555c", | ||
"slug": "rest-api", | ||
"uuid": "2abe6eed-c7e4-4ad7-91e3-778bc5176726", | ||
"core": true, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
rest-api
still has some sizable issues; it should probably be a side exercise for now. It might merit promotion when it is more developed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree it looks like it's better as a side exercise.
take `"deprecated": false` out Co-Authored-By: F3PiX <emcoding@pm.me>
@cmccandless Back to you. Made the changes. 🎉 |
I think this looks good! As always, we may find the need for further tweaks down the road, but I think this should help with the difficulty curve on this track. |
Cool! Yeah, there will be tweaks needed, but I hope this helps. |
@iHiD, would you kindly? |
It seems to have magically done it itself! :) |
Thank you both! |
This is to get you all started with the rearrangement of the track, as proposed in #1614
Please note that I don't know Python; this was done based on the changes I made to the Ruby track.
Hope it helps!
Bob, Allergies, Sum of Multiples, Kindergarten, Grade School, Saddle Points, BinarySearch, List ops, Bookstore, Markdown, Rest-api.
I added commits for each of them, so that you can easily revert them. My changes are based on either considerations I made to the Ruby track, or a rough estimation in regard to the changes in this PR.
Closes #1614
Maintainers To do :