Reflect

docs/schedule.md

@@ -20,7 +20,7 @@ Monday   |15:40-16:00|Lars   |Confidence and retrospect
 |||||
 Tuesday  |09:00-10:00|Lars   |[Software development life cycle](./introductions/sdlc.md)
 Tuesday  |10:15-11:00|Richel |[Issues](project/issues.md) and [kanban board](project/kanban_board.md) and [team roles](project/team_roles.md)
-Tuesday  |11:15-12:00|Richel |[assert](algorithms/assert.md), [TDD](tdd/README.md)
+Tuesday  |11:15-12:00|Richel |[assert](algorithms/assert.md)
 Tuesday  |13:00-14:00|Richel |[TDD](tdd/README.md)
 Tuesday  |14:15-15:00|Richel |[TDD](tdd/README.md)
 Tuesday  |15:00-15:40|Richel |[Formal testing framework](testing/testing_framework.md)

reflections/2024_autumn/20241122_richel.md

@@ -29,3 +29,41 @@ It should be scheduled after run-time speed optimization.
 I predicted I would be tired at the end of the course and I predicted
 these would be my worst lectures, as I felt the same in earlier
 iterations of the course.
+
+## Whole course
+
+I feel I did a reasonable job.
+We all (teachers and learners) helped create a warm atmosphere in the course.
+
+My favorite improvement was my exercises: thanks to the Retrospect at day 1,
+I suddenly understood what was needed. 'No plan surives first contact with
+the enemy', they say, for me it was more that the retrospect made me
+prioritize better. 
+
+I would now say that a good exercise is:
+
+- Clearly described what to do
+- Has a worked-out solution
+- If possible: has multiple skill levels
+
+I want to have this in all my exercises, before next course iteration.
+
+- [ ] Make all exercises like that
+
+I enjoyed the team of teachers. My favorite is how we can flat-out
+disagree, without any drama.
+
+The course is a complex beast, with many dependencies between lessons.
+I wonder why we do not have written a script to check if our schedule holds?
+
+- [ ] Make stub of script, to be used in CI
+
+I've added domain-specific knowledge, in the form of biology.
+I think it should be general things we have exercises of
+
+- [ ] Remove biology things
+
+I think the project should be worked on more and be simplified.
+Maybe start with a proper/pre-fab requirements list.
+Branch of from the main function more.
+