I'll start working on a syllabus for the track. Many basic concepts can probably be adapted from other functional languages such as elm.
In the x86-64 track, I wrote many concepts and only then added their corresponding exercises. This allowed me to have a general high-level view of the entire syllabus before deciding where each topic would fit. I'll do the same here.
One thing I'll do differently, though, is keep the concepts in a separate "draft" folder. I didn't know at the time but if a concept is added to a track, even without its exercise and even if the syllabus is still wip, it is exposed to students in the track's update feed.
Eventually we will need to update the test-runner to at least v2 before releasing the syllabus to students. I think this won't be too difficult, but it might require making some changes to the test suite so it passes along the test code and other necessary information to the test runner. But this is something for later.
I'm hoping to add maybe one or two concepts each week.
I'll start working on a syllabus for the track. Many basic concepts can probably be adapted from other functional languages such as
elm.In the x86-64 track, I wrote many concepts and only then added their corresponding exercises. This allowed me to have a general high-level view of the entire syllabus before deciding where each topic would fit. I'll do the same here.
One thing I'll do differently, though, is keep the concepts in a separate "draft" folder. I didn't know at the time but if a concept is added to a track, even without its exercise and even if the syllabus is still wip, it is exposed to students in the track's update feed.
Eventually we will need to update the test-runner to at least v2 before releasing the syllabus to students. I think this won't be too difficult, but it might require making some changes to the test suite so it passes along the test code and other necessary information to the test runner. But this is something for later.
I'm hoping to add maybe one or two concepts each week.