-
-
Notifications
You must be signed in to change notification settings - Fork 652
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
Choose core exercises structure #794
Comments
If you've not already seen this, it should be useful exercism/discussions#175 (comment) |
I'm going to be mulling these over in my head for awhile as we have a ton of exercises. For starters what does everyone think our most simple exercises are? These are our difficulty 1 exercises: |
I'm gonna say our easiest exercises are:
Then very similar:
A little harder but also similar:
This is my rough read on the first few exercises. |
tbh I'm finding this quite hard to conceptualise in my head how to sort the exercises, and have been kind of avoiding it. I'm going to need to sit down with a pen and paper and map it out I think. |
Me too. It is really hard even doing baby steps like above. When confronted with a problem I don't know how to fix my first instinct is always to build something just to help get my head around the problem. The visualizer is awesome, and great for seeing the track come together, but at the same time I am much more of a command-line show-me-in-text guy. I spent some time over the weekend making a quick and dirty exercism-config-to-csv command line tool that would let me look at configs/sort them like a spreadsheet. Some more quick tooling and adding a descriptive field (#798) may make this much easier. Trying to map it out all at once is too prohibitive. We should start with some baby steps: identifying core and perhaps sequencing the difficulty 1&2's then move on from there. Ultimately we will get through this, take a look at our early work and think, "nope it can be done better" and fix it. We will make some errors, but that is part of the process and we can always fix later! |
Some more data that may be helpful, this is the difficulty -> exercise listing:
(I've been building some stuff to help us get more information from the track configuration(s): dump track configuration, get all track configurations as a single file and run reports against that file.) |
FWIW, here are the core exercises in other tracks:
|
This PR stems from exercism#717, exercism#794, exercism#805, exercism#813, exercism#825 Closes exercism#828, exercism#829, exercism#830 It should be noted that while my name is attached to this commit, this PR would not have been possible without the hard work and insights of Tom Leen (@tleen). For Exercism v2, codename Nextercism, the structure of exercises will change. It will no longer be a linear progression, rather there will be a series of core exercises that will lead on from one another with mentor approval. These core exercises will in turn unlock other exercises that can be completed as and when. This change implements the new exercise progression structure.
This PR stems from exercism#717, exercism#794, exercism#805, exercism#813, exercism#825 Closes exercism#828, exercism#829, exercism#830 It should be noted that while my name is attached to this commit, this PR would not have been possible without the hard work and insights of Tom Leen (@tleen). For Exercism v2, codename Nextercism, the structure of exercises will change. It will no longer be a linear progression, rather there will be a series of core exercises that will lead on from one another with mentor approval. These core exercises will in turn unlock other exercises that can be completed as and when. This change implements the new exercise progression structure.
* [nextercism] Restructure config.json This PR stems from #717, #794, #805, #813, #825 Closes #828, #829, #830 It should be noted that while my name is attached to this commit, this PR would not have been possible without the hard work and insights of Tom Leen (@tleen). For Exercism v2, codename Nextercism, the structure of exercises will change. It will no longer be a linear progression, rather there will be a series of core exercises that will lead on from one another with mentor approval. These core exercises will in turn unlock other exercises that can be completed as and when. This change implements the new exercise progression structure.
* [nextercism] Restructure config.json This PR stems from exercism#717, exercism#794, exercism#805, exercism#813, exercism#825 Closes exercism#828, exercism#829, exercism#830 It should be noted that while my name is attached to this commit, this PR would not have been possible without the hard work and insights of Tom Leen (@tleen). For Exercism v2, codename Nextercism, the structure of exercises will change. It will no longer be a linear progression, rather there will be a series of core exercises that will lead on from one another with mentor approval. These core exercises will in turn unlock other exercises that can be completed as and when. This change implements the new exercise progression structure.
* [nextercism] Restructure config.json This PR stems from #717, #794, #805, #813, #825 Closes #828, #829, #830 It should be noted that while my name is attached to this commit, this PR would not have been possible without the hard work and insights of Tom Leen (@tleen). For Exercism v2, codename Nextercism, the structure of exercises will change. It will no longer be a linear progression, rather there will be a series of core exercises that will lead on from one another with mentor approval. These core exercises will in turn unlock other exercises that can be completed as and when. This change implements the new exercise progression structure.
* [nextercism] Restructure config.json This PR stems from exercism#717, exercism#794, exercism#805, exercism#813, exercism#825 Closes exercism#828, exercism#829, exercism#830 It should be noted that while my name is attached to this commit, this PR would not have been possible without the hard work and insights of Tom Leen (@tleen). For Exercism v2, codename Nextercism, the structure of exercises will change. It will no longer be a linear progression, rather there will be a series of core exercises that will lead on from one another with mentor approval. These core exercises will in turn unlock other exercises that can be completed as and when. This change implements the new exercise progression structure.
* [nextercism] Restructure config.json This PR stems from exercism#717, exercism#794, exercism#805, exercism#813, exercism#825 Closes exercism#828, exercism#829, exercism#830 It should be noted that while my name is attached to this commit, this PR would not have been possible without the hard work and insights of Tom Leen (@tleen). For Exercism v2, codename Nextercism, the structure of exercises will change. It will no longer be a linear progression, rather there will be a series of core exercises that will lead on from one another with mentor approval. These core exercises will in turn unlock other exercises that can be completed as and when. This change implements the new exercise progression structure.
From #717:
If you haven't already, now would be a good time to do the following:
- [x] add a rough estimate of difficulty to each exercise (scale: 1-10)- [x] add topics to each exercisecore: true
, and delete theunlocked_by
key)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.
The text was updated successfully, but these errors were encountered: