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

Re-adjust and limit difficulties for exercises? #793

Closed
sshine opened this issue Dec 14, 2018 · 3 comments
Closed

Re-adjust and limit difficulties for exercises? #793

sshine opened this issue Dec 14, 2018 · 3 comments

Comments

@sshine
Copy link
Contributor

sshine commented Dec 14, 2018

In exercism/rust#460, four difficulties were picked: 1, 4, 7 and 10. I also believe that choosing between four difficulties results in a clearer cut, and I think the Haskell track should adhere to the same four categories. Subsequently we can adopt the CI hooks that verify difficulties from exercism/rust#503; as for the assertion that exercises are sorted by difficulty, await a final decision in #790.

@sshine sshine changed the title Re-adjust and limit difficulties for exercises Re-adjust and limit difficulties for exercises? Dec 14, 2018
sshine added a commit that referenced this issue Dec 17, 2018
Nucleotide Count has several reasonable implementations and learning
goals. Mentor notes are made available in exercism/website-copy#654 and
the discussion to replace some core track exercises is advanced in #761.

Until either its difficulty has been adjusted (#793) or another order
has been picked (#790), continue to order config.json by difficulty.
@petertseng
Copy link
Member

We might even consider only using distinctions the site considers significant.

https://github.com/exercism/website/blob/49450d71253cfbbb49ad7c4660ad74e060a315dc/app/controllers/my/side_exercises_controller.rb#L12-L18

https://github.com/exercism/website/blob/49450d71253cfbbb49ad7c4660ad74e060a315dc/app/helpers/exercise_helper.rb#L17-L23

In other words, we might select just one from each of the three categories. Perhaps 1, 5, 10, for example. Having a track-level distinction between 4 and 7 in our JSON file would only be necessary if we wanted to use it for some purpose that we discuss in this issue.

@sshine
Copy link
Contributor Author

sshine commented Jan 7, 2019

Good point!

For now I only really care about the "Easy" .. "Hard" labels.

I intend to propose a restructure of the core track following a method that @F3PiX is heading once other tracks have gone through this; asserting difficulties in other granularity than 1-5-10 or 1-4-7-10 may apply then, so I'll wait a little.

@sshine
Copy link
Contributor Author

sshine commented Oct 17, 2019

I am closing this issue for now, and it can be returned to later.

@sshine sshine closed this as completed Oct 17, 2019
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

No branches or pull requests

2 participants