Evaluation 2025-05-08¶

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

- A: exercises related to the project; pair programming
- A: group work
- A: presence of the teachers in the breakout rooms
- A: group work, interaction with instructors, material, Copilot
- A: pair programming, building on work from previous days
- A: Introduction of different tools that can be used (e.g Mermaid)
- A:
- A: practical exercises, continuing to use issues and branches
- A: Small group of 2 work better in online interactions (easier to share responsibilities)
- A: Practice, Pair-programming together with teachers helping

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

- A: not enough time to finish excercises
- A: getting tired from reading
- A: not having enough time to test to implement the different concepts presented, starting to look at the answers for the exercises too late
- A: already familiar with basic object-oriented programming principles so it wasn't much new stuff, exercises went pretty quick
- A:
- A: lack of comprehension of concepts, there were some parts that I needed to ask Copilot to help
me understand. There wa
- A: Trying to perform the prievous steps (Open issue, create new branch, assign work...) can take much time and reduces the direct work that we should actually do
- A: Quite a bit of content to go through in the time slots available
- A: too many errors to handle in CI workflows
- A: Lack of time to finish excercises, especially, after questions asked or interesting discussions

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

- A:
- A: illustrate all these concepts on our Weather station project
- A:
- A: maybe have an hour reserved every day to try out what we learned and implement things on the project
- A: make a wider range of difficulty for the classes we are supposed to implement
- A: if we progressed more on the project it might have been easier to understand how to use things when you are trying to solve a "real" problem
- A:
- A: More examples for some cases (just having them available in the documentation for later reading would help). Maybe a full example in the end of a topic to summarize the points.
- A: All the sources for reading are good and can be kept for home reading while for the classes reworked(shortened/fused/restructured) text could be prepared. To keep essense and spare time
- A:

What will we do(Act) [Teachers only]¶ -L lars will write a complete project for weather project with lots of code smell and design smell

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!

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

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

I know what modular programming is

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

I can criticise functions

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

I can give a function a proper name

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

I can give some features of good function design

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

I can write a class to express what the data it contains

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

I understand the type of relation 'composition'

- A:
- A: 0
- A: 2
- A: 3
- A: 5
- A: 3
- A:
- A: 4
- A:
- A:

I understand why function design is important

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

Iterative refactoring

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

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

- A: 1
- A:
- A: 3
- A: 5
- A: 3
- A: 4
- A:
- A:
- A: 4
- A:

Learn the definition and characteristics of an object,

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

Recognize and address tight coupling in code to improve modularity.

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

Recognize the importance of relationships between classes including coposition and association

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

Understand the benefits of object-oriented development

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

Understand the concept of code smells and design smells

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

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

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

Feedback by email¶

From a learner:

Hi Richel (and Lars and Björn). Just popping in to say that I won't be able to attend the rest of the course. Entirely due to bad planning on my behalf. I like the 1.5 days I joined. The materials are fantastic. Have a good rest of the week!