Skip to content

Reflection Day 3

  • Author: Richel
  • Date: 2026-05-06

This day was fun.

  • TDD three hours is good
  • TDD and pair programming on same day is good

Let's take a

Day 3

What helped us learn

  • Working together in paired programming.
  • The lecture with link instruction
  • The demos were very helpful, especially when two people worked together. Thanks to Richell and Stefan. Very helpful TDD and Pair programming session, with shared knowledge and helping each other.
  • The pair programming was very helpful.
  • Paired programming was good, particularly for people that are not very experienced.
  • I actually really like the practical demos Richel presented. They do not have to be long (1-2x 15-20mins? per day), but it is a great intro. Pair programming was a fun new experience.
  • Communication, teamwork, role switching, and explaining our ideas helped us learn. Reviewing the code together and solving problems as a pair made the task easier to understand.
  • Helping each other
  • Teacher explanations before the pair-teaming. - The teacher's demonstration of the pair-programming with a student. - The pair-teaming discussions/work - The pair-programming.
  • Working with different people was helpful! I liked using is_even in the is_odd TDD examples. I think moving onto the project when you finished examples was also helpful
  • The live-up exercise with the teacher showing how to pair-programme
  • Changing groups for the pair programming was nice and helpful.
  • I've never tried TDD, but I realised that it is a good strategy.
  • Breaks
  • Changing groups allowed us to experience different types of collaboration.
  • Seeing how TDD is done was very helpful
  • Having different levels allowed knowledge sharing.
  • Having an introduction of what to do in pair programming helped.
  • Having to switch between driver and navigator was helpful.

What held us back

  • Not really sure

Great!

  • I was confused about some function which doesn't reasonable

I wish I knew which ones :-)

  • I can't complain, I really enjoyed the practice today.

Yay!

  • Switching groups mid-job (during one session) was disruptive.

It is. And I should do it. We agree here that it is disruptive.

  • There was probably not enough time to complete all the exercises, but that was probably not the aim. There was enough time to grasp the concepts

Nice.

  • Sometimes, the division of work in teams is challangeing when they are changing frequently. I would prefer either keeping the same team whole day or a predefined strategy on who does what

I should address this.

  • Limited skills and knowledge held us back, especially in my case. I needed more time to understand the task and follow the coding process, which made the work slower

  • VS Code giving weird git errors

I agree.

  • Nothing specially, today.

Yay.

  • I think a little more structure about how to set up the learners folder would be helpful like making a folder to put the file in on the first day. Also should you work on your own project or just copy

  • For me it was a little more difficult to know what was expected from every exercise

I should add answers to each question.

  • Having people leaving before left people without pairs.

This is indeed the reality we need to work with...

  • TDD is difficult to embrace in a single session, it is a way of work, but that's fine.

I agree.

  • Having the choice of what to work on was a bit disruptive, having only the project or only the functions to work on would have been better.

I will consider this.

  • Not understanding how to check if a function existed was a problem.

I can imagine: I have no idea how to do this either ...?

what can we improve to help us learn better

  • A bit long lecture and clear instruction

I will consider this, however, I wish I knew which session this was about. All?

  • I liked that today we have TDD and Pair programming. Maybe for other students in the next course, you can keep these two sessions for the same day as it helps in reinstating the idea.

Great idea!

  • A more structured choice of the problems to work on would help.

I will consider this.

  • There were some wrong statements on the coding, and we lost some time to think about function names, etc.

I wish I knew which function names. As far as I know, I always explain all functions what they do ...?

  • [ ] Check if all functions are described

  • Next time, it might be good to use a programming language where you have extensive experience.

I can imagine that one feels a bit out of place when not being able to write Python scripts. However, this is a prerequisite.

  • I really likes assignment in Pair programming section with clear time frame and structure (each read one article, then discuss and produce md summary). Would recommend to replicate!

I agree I should do this more often!

  • We can improve by communicating more, asking questions when we do not understand, and switching roles more often.

I see that pair programming does not always work out equally well.

  • We can also explain each step slowly, practice more, and review basic concepts before

I see that pair programming does not always work out equally well.

  • The program for the day is already good enough. 😇

Yay!

  • I think a "helpful" page would be good with packages or things to use in the project

I will consider this ...

  • Maybe compare some of the code? Or instead of having too many functions, just use one and debate of the different approaches between each group

I will consider this ...

  • A variety of 'jobs' of the project level (like weather) would allow people to choose a different project with a different pair

I will consider this ...