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 progression through exercises #80

Merged
merged 2 commits into from
Aug 28, 2017
Merged

Conversation

SaschaMann
Copy link
Contributor

See exercism/discussions#175.

First attempt at a progression order through the track. Looks like this:

image

@jonmcalder
Copy link
Member

Cool! FYI, my understanding is that (for now at least) only core exercises should unlock other exercises.

e.g. from exercism/discussions#75:

Aside from those initial optional exercises, all other optional exercises (core: false) should be unlocked_by the slug of a (a single) core exercise.

You've got sequential unlocking in nucleotide-count -> scrabble-score -> etl

@SaschaMann
Copy link
Contributor Author

SaschaMann commented Aug 5, 2017

@kytrinyx' PR #73 mentioned the following:

Non-core exercises depend on only one exercise (unlocked_by: ). At the moment we are assuming that this is a core exercise, but there is no reason that it needs to be.

so I thought such progression would also be fine. Javascript also uses it according to the visualisation example.


Added some non-core, non-bonus exercises so we fill the following criteria:

If possible, leave 3 or 4 simple exercises as (core: false, unlocked_by: null), as this will provide new participants with some exercises that they can tackle even if they have not finished the first core exercise.

@jonmcalder
Copy link
Member

Ah ok cool. I must have overlooked that somehow! My apologies.

@kytrinyx
Copy link
Member

kytrinyx commented Aug 5, 2017

I'm pretty sure what you have here will work. Once we get the prototype launched we'll be able to test it out and tweak it if not.

@SaschaMann SaschaMann merged commit 51e5609 into master Aug 28, 2017
@SaschaMann SaschaMann deleted the nextercism-progression branch August 28, 2017 19:32
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.

None yet

3 participants