Evaluation Day 2¶
We used a Retrospect to evaluate.
What helped us learn¶
- It was good
- The discussions we had in the break out groups. I also think the exercises made us think and reflect about hte topics in an interesting way.
- The hands-on exercises
- The break zoom with an expert helped me to learned a lot
- The material, exercise and discussions with partners. Peer groups was very very helpful.
- The interactions in the small groups helped a lot.
- Short theoretical sessions, followed by short hands-on exercises.
- Writing code in vscode. Hands on experience. Exercise descriptions and answer examples were more explicit and concrete. Good pace.
- The documentation, the group exercises, the questions
- Exercise sessions
- The course was very didactic, and the interaction in group work helped me learn a lot.
- People helping each other out
- the material, and when the material was flawed or unclear, the the teacher clairifed. The most helpfull was the direct supervision by Lars on how to commit and sync in VS code
- How interactive the course is. We are encourage all the time to discuss and collaborate between us
- Practical exercises with VCS and Git. We had problems and then we solved them in pairs or with help of the teacher. It was very good to take the time to actually solve the conflicts. Deep discussions.
- The short theory explanations before the paired sessions - The discussion in paired sessions
- Discussions
- The coding sessions in the breakout rooms were good. I liked the assert statements session, I like how it imported os for file reading because that's something we will use in our project for the class
- Reading and trying the code by ourselves. Testing and then reading the answers you provided. The slow pace of the course Peer guidance Using the expert learners made everything easier. Be on time was great, so that the breaks are not missed and no time is wasted. Clear course material course material quite compact! structure of the course and peer discussions Having the teachers come around in the breakout rooms was helpful Meeting others
What Held us back, what stopped us from learning¶
The examples not matching up with vs code Could not come up with any road blocks Too little hands-on coding Going well Time constraint and extensive exercise. The afternoon sessions are harder due to the timing (after lunch, already tired). Nothing, all good. Mostly usure about time slot for the exercises because of accelerated schedule. Would be good to have some type of timer, or clear time frame. too many breaks maybe Some concepts were difficult at first because I am still getting familiar with Git and programming workflows. Waiting in the main room for others to finish Too slow pace. And too much discussion of what the students are guessing about the topic, while the correct answer was not discussed as much. Nothing. The main issues was the short time to go through all the exercises. My own preparation I had to spend quite a long time to help another student who hadnt done the preparations before the course. It was ok to do but it took away a lot of time from my own learning. Tiredness in the afternoon The less structured nature of the afternoon hindered a bit. Weird git errors in VSCode
What can we do to improve, how can learning be improved¶
Maybe some more initial steps can be done in preparation for people who have not used git before Not sure Some exercises did not include answers A bit more lecture Maybe not so many exercise for the assert section. It was very re-iterating and good but maybe can be used for one's own pace instead of in the class. The afternoon session could be more structured. Some people might a bit shy with questions. I guess having a place where they can post anonymous questions, might be good for them. And then address those questions during the lessons or afterwards. More specific information about time given/needed for exercises. Mark the most important part of the sections to be able faster move toward the exercises. maybe explain polymorphism Learning could be improved with more guided practice time for Git, GitHub, and VS Code workflows Probably the content of today could be learnt using much less than a whole day by having access to the material and using AI to help explain what i didnt , and then doing exercises together afterwards Maybe for the exercises of today's session the break room could have been with four-five students instead of pairs. There were more theoretical questions and more people could create a better discussi Write some code in pairs and then swap so other people can read and compare. Maybe, have 5-10 minutes to go through the exercise answers with the instructors would be a good idea to improve understanding. perhaps some fore focus on merge conflicts and different ways of dealing with them. (perhaps it is outside of this course's scope though). A longer lunch break. More specific instructions when writing code (do it through vs code etc.)