You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For simplicity, new exercises are being implemented as bonus exercises, meaning that unlocked_by is set to null in config.json.
Therefore after the new exercises are merged, we should probably consider:
Changing the core exercises (to include some of the current bonus exercises, or some of the new exercises).
Turning the remaining bonus exercises into side exercises.
Tweaking the exercise order.
Tweaking the difficulty ratings.
Changing config.json to follow this proposed ordering, which may become part of configlet in the future. This should help reduce diff noise when reordering exercises later.
Changing the topics be more useful and specific to Nim.
I don't currently have strong opinions on the track structure, but other tracks have put significant thought into it. We should consider (or steal) their ideas, at least as a starting point. I'll write some suggestions later. Let me know if you have any thoughts.
Regarding difficulty: most of our currently implemented exercises are relatively easy. Some tracks use a restricted set of ratings (such as: 1, 4, 7 and 10). If we do this, I think nearly all our our current exercises should be difficulty 1 so that we can have a clear difference later between easy and medium difficulty.
It's also easier to implement good solutions in Nim than in many languages.
For simplicity, new exercises are being implemented as
bonus
exercises, meaning thatunlocked_by
is set tonull
inconfig.json
.Therefore after the new exercises are merged, we should probably consider:
core
exercises (to include some of the currentbonus
exercises, or some of the new exercises).bonus
exercises into side exercises.config.json
to follow this proposed ordering, which may become part ofconfiglet
in the future. This should help reduce diff noise when reordering exercises later.topics
be more useful and specific to Nim.I don't currently have strong opinions on the track structure, but other tracks have put significant thought into it. We should consider (or steal) their ideas, at least as a starting point. I'll write some suggestions later. Let me know if you have any thoughts.
Some recent work by other tracks:
Regarding difficulty: most of our currently implemented exercises are relatively easy. Some tracks use a restricted set of ratings (such as:
1
,4
,7
and10
). If we do this, I think nearly all our our current exercises should be difficulty1
so that we can have a clear difference later betweeneasy
andmedium
difficulty.It's also easier to implement good solutions in Nim than in many languages.
Current Nim track structure
configlet tree config.json --with-difficulty
The text was updated successfully, but these errors were encountered: