How this course works
Where? |
ex SISSA Building, Room E |
When? |
Mon - Fri (9:00 to 17:00) |
Questions? |
|
Grading
All participants will be assigned a group number. Each participant is required to keep notes of their progress along the exercises and summarize them in their own words by the end of the day in a short written report. This report has to be submitted in their GitHub fork of the course repository. The final grade will be 40% based on the submitted reports, 30% on the successful completion of the exercises and 30% on the small quizzes throughout the course.
Activity |
Grade |
|---|---|
Reports |
40% |
Completion of Exercises |
30% |
Quizzes |
30% |
Warning
Start taking notes immediately! You have to be able to summarize what you did in your own words! Past year’s best students started on their reports while they were working on the exercises. That way the amount of work needed afterwards becomes minimal.
Reports
The reports are only needed for the exercises.
Reports should not be a 1:1 copy of the instructions, but instead be a summary of what you did in a way that could be understood by someone else.
It should highlight what you learned and/or problems that you might have encountered, and how you resolved them.
Each configuration file that was created or modified by you needs to be committed to your GitHub repository. You don’t need to store each version, just the final version after each exercise.
Warning
Reports that are submitted with no files will automatically have 0 points.
Note
The reports have a dual purpose. One the one hand, they help us assess if you have successfully completed the exercise. On the other side, it helps you as you move along, since each exercise builds on the results of the previous one.