Introduce Homework

[domenicodev]

Introducing Homework for Students

[teohaik]

@domenicodev for the work here! One open topic that should be clarified is: Where are participants going to submit their solutions? Now we suggest they push to code to github but they will notify us about this submission? Also how are we thinking about the grading/evaluation of their submissions?

[domenicodev]

@domenicodev for the work here! One open topic that should be clarified is: Where are participants going to submit their solutions? Now we suggest they push to code to github but they will notify us about this submission? Also how are we thinking about the grading/evaluation of their submissions?

For the early phases(alpha/poc):

1. Students fork/clone this repo
2. Students push in their own branches and/or open PRs against them
3. Students send us the link and we either review it on github, or clone the repo locally.
4. At the beginning of every day's session, we spend the first 20-30 min on reviewing and explaining the code of 1 or 2 students. So others can take notes and fix after.

In future:

1. We use classroom.github.com (need to investigate on if we need to create an Organization for every bootcamp, or can use a global one)
2. We (optionally) create a new repo for the exercises (not in this repo) to keep it clean
3. Via classroom, we "assign" the exercises to the students, and provide details on how to make it work;
   I am investigating on it but it seems like they can create their own private repos, e.g. sui-bootcamp-exercises-USER on their profile, and the dashboard of the classroom can track it.
4. The template (or, if not, via gh actions/classroom) will include branches for every exercise: day1-exercise, day2-exercise, ...
5. Students will work and "push" on these branches, and manually (or automatically, if possible via gh actions) create PRs for branch->main, so we can review the changes.
6. We will do the same as we did at point 3. of alpha phase, and optionally also review others if we have free time at home/after finishing the day session, if necessary.

A good practice in both approaches, would be that while we "read and fix" the code, we add comments on the PRs so students can circle back and read them.

[domenicodev]

Also, ideally, this homework will also have a solution branch (e.g. homework-solution if in this repo, solution if in separate), so it will be easier for teachers to review.
Students' solutions may vary but of course they'll have common points and/or architecture, if correct.
Even for the open questions/answers.