Exercises
Introduction
Every student need return exercises information to JAMK GitLab using a given template repository. Information need to be available when course is running and at least when the course will be evaluated when it ends.
Jamk/IT GitLab - Full Stack exercises repository
Student need to fork Full Stack exercises repository template first to his/her own account. Use private visibility level, so your exercises solutions are not visible to other students. Remember manage members and invite teacher (Pasi Manninen) as a reporter role, so teacher can evaluate your work.
Fork this repository to your own account:
Diary of exercises
The student keeps a record of the exercise tasks he has completed in repository README.md file. For each exercise task, the student must evaluate by points how much of the task's requirements he/she has completed. If the main requirements of the task are met, it is enough for full points. The student can briefly comment on the scoring he/she has assessed.
Teacher will monitor studends work. When asked, the student must be able to tell about the central technical logic of the solutions used in the exercises. The solutions to the exercises must be available via the repository until the completion of the course has been approved.
Student need to update the diary of exercises all the time when course is running. Exercise solutions should be easy to check. A good idea is to combine the tasks of a certain exercise series in a suitable way, use already made exercise directories.
Example
First three exercises are done in a below example. Two exercises are completed fully and small issue with third exercise. Remember that you can later come back to those exercises which are not fully completed. Just ask help from the teacher or other students and learn more - and complete exercise and update your diary of exercise. All exercises will be evaluated when the course ends.
