Evaluation¶

Date: 2025-10-28
Day: 4

Analysis¶

All confidences

Average confidences per questions

Confidences per question

Retrospect¶

What helped us learn (let us move forward) 2 min

A: As usual, group exercises
A: The possibility to ask questions and get extensive answers. Thank you for your patience!
A:
A:Group work, practical exercises
A:
A: Continous Integration and group work
A: Nice group work.
A: The team exercises, in particular for writing clases. The session on automated testing workflows within GitHub (and locally) were very interesting.
A:
A:
A: the testing exercise was good! Finding out the options to automate the testing was nice.
A: Ruff - was a good extension

What stopped us from learning (What held us back) 2 min¶

A: Maybe the schedule was a bit messy today, I would gladly have had class design before OOD
A:
A: I found some text, in particular the Object-oriented programming section, hard to read because of typos. I wish it wasn't so much like bullet points. It often asks us about a concept and only give bullet points but we have to go to some alternative reading material to find the answer. Many concepts were remain a bit abstract even after the explanations...I also got lost with many exercises because they were a bit vague or use terms before getting explanations about it (e.g., refactoring)
A: Maybe some more clarifications about object oriented programming would have been helpful. Less theory and more examples.
A:
A: assignments were not always clear, confused about what we should actually do...
A: a bit confused about the reverseb classroom situtation, since we didn't have time to read up upon it before (and text didn't alwyas provide the answers that were asked there)
A:
A: Most concepts introduced today was a hard to intrepret in our discipline specific examples
A: The concepts of object and class were a little hard.
A: Time, short answers, no too deep explainations and typos in documentation. -A:
A: Unit test lessons were unclear
A: Little time to complete all the exercises, would have appreciated less to do but with more time to focus

What could we do to improve learning (What can we invent) 2 min¶

A: I think in general it would be beneficial to focus on easier tasks and not too much on the weather exercise, with more discussion. Baby steps and more time to digest.
A:
A: Better material with less bullet points and more structure and explanations would help
A: As much as I appreciate working with teams, sometimes I wish I could read on my own without other people around. I find it distracting because I feel pressure to finish faster. I prefer when we get examples explained by the teacher before diving into the exercises.
A: more explanation of terms and basic "vocabulary", more straigth forward assignments, clearer instructions
A:
A: More examples before working on our own, sometimes it is hard to figure out everything on your own
A:
A: Also, sometimes the concepts are too simple and feels difficult to relate to our discipline, maybe more examples to show how it looks would be appreciated
A: Maybe a solid example/exercises on object & class diagrams would be good
A:
A: More self-contained examples with answers that we can revisit later on. Add more links to external videos on hands-on coding for every or most concepts.

What will we do(Act) [Teachers only]¶

Confidence Report: (maximum 10min) You can leave when you are done.¶

Give you confidence levels of the following statements, using this scale:

0: I don't know even what this is about ...?
1: I have no confidence I can do this
2: I have low confidence I can do this
3: I have some confidence I can do this
4: I have good confidence I can do this
5: I absolutely can do this!

I understand why Continuous Integration is useful

A: 5
A: 5
A: 5
A:
A: 3
A:
A:
A:
A:
A:
A:
A: 4

I can find the error messages given by the Continuous Integration tests

A: 5
A: 5
A: 5
A:
A:4
A:
A:
A:
A:
A:
A:
A: 5

I can (choose to) write code that is Good Enough

A: 4
A: 3
A: 4
A:
A:
A:3
A:
A:
A:
A:
A: 5
A:

I understand what a Semantic gap is?

A: 4
A: 1
A: 3
A:
A:1
A:
A:
A:
A:
A: 3
A:
A:

I Comprehend the principles of object-oriented development, such as information hiding

A: 5
A:
A: 4
A:
A: 3
A: 3
A:
A:2
A:
A:
A:
A:

I know what modular programming is

A: 3
A: 5
A: 3
A:
A: 3
A:
A:
A:3
A:
A:
A:
A:

I have an idea when use classes is worth it (and when not)

A: 3
A:
A: 4
A: 3
A: 4
A:
A:2
A:
A:
A:
A:
A:

I can give some features of good class design

A: 4
A: 2
A:
A:
A: 2
A:
A: 2
A:
A:2
A:
A:
A:

I can write a simple class

A: 4
A: 3
A:
A:
A:3
A:
A: 3
A:
A:
A: 4
A:
A:

I understand the type of relation 'composition'

A: 3
A:
A: 2
A:
A:2
A:
A: 2
A:
A:
A: 1
A:
A:

Iterative refactoring

A: 5
A: 2
A:
A:2
A:
A: 1
A:
A: 3
A:
A:
A:
A:

Learn about common interfaces, protocols, and their role in modular programming.

A: 3
A:
A:
A: 1
A:
A: 1
A:
A:1
A:
A: 1
A:
A:

Learn the definition and characteristics of an object,

A: 5
A:
A: 3
A:
A: 3
A:
A: 4 (after intensive discussion with Lars)
A:
A:2
A:
A:
A:

Recognize and address tight coupling in code to improve modularity.

A: 3
A:
A:
A: 2
A:
A: 3
A:
A: 1
A:2
A:
A:
A:

Recognize the importance of relationships between classes including coposition and association

A: 4
A:
A:
A: 1
A: 1
A:
A: 2
A:2
A:
A:
A:
A:

Understand the benefits of object-oriented development

A: 4
A:
A: 3
A:
A:
A: 4
A:
A:2
A:
A:
A:
A:

Understand the concept of code smells and design smells

A: 5
A: 4
A:
A: 3
A:
A: 2
A:
A:
A:2
A:
A:
A:

Understand the definition and structure of a class as a collection of objects

A: 5
A:
A:
A: 2
A:
A: 4
A: 2
A:
A:
A:2
A:
A: