Skip to content

Meeting 2026-08-25

FYI

  • Richel has updated the guest teachers
  • The PF website asked for a polyfill login. This was malicious code. Richel removed it for PF and all other courses that had this in their mkdocs.yaml setup
  • Anders said maybe, needs clear instruction, RB will do so.

Discussion

  • Course allegiance: currently we aim to be a CodeRefinery course. I, RB, think that a collaboration with NBIS would be beneficial, mostly for publicity. What about we call the course a collaboration between CodeRefinery and NBIS?
  • Pro: wider reach in finding participants
  • Con: it is mostly strategic

  • Votes:

    • RB: Yes [DECIDED]

  • When is the next course?

  • RB: May 2027, November 2027, May 2028, November 2028, etc. This seems to be the tradition. What about for next course iteration:

    • 2027 week 18: May 3-7 : No, due to red day
    • 2027 week 19: May 10-14: Yes [DECIDED]
    • 2027 week 20: May 17-21
    • 2027 week 21: May 24-28 What about for next next course iteration:
    • 2027 week 43: October 25-29: No, höstlov
    • 2027 week 44: November 1-5: No, due to red day
    • 2027 week 45: November 8-12: Yes [DECIDED]
    • 2027 week 46: November 15-19
    • 2027 week 47: November 22-26

  • What will the next course schedule be?

  • RB: I estimate that around 11 hours become available (see the 'Course schedule' section below). What about we
    • Decide what to do with the hours that may come free: remove or take over?
    • Add our wishes for what we want to teach
    • Then I, or someone else, comes with a new draft schedule, to be discussed next meeting.

Course schedule

Changes are:

  • unsure who will take design part of the Monday afternoon
  • May frees up these hours:
    • Monday 11:15-12:00 'Define and plan project': RB volunteers to take over this hour
    • Monday 13:00-15:40 'Requirements and risk assessment introduction': no volunteers yet No volunteers just yet.
  • basic git workflow is now a prerequisite
  • BC suggests 'basic' is defined only as 'using one branch'
  • Frees up these hours:
    • Tuesday 10:15-11:00 ('Version control')
    • Can be removed: BC, RB, ML
    • Tuesday 11:15-12:00 ('Integrated development environment')
    • Can be removed: BC, RB, ML
    • Tuesday 13:00-14:00 ('Merge conflicts')
    • Can be removed: BC, RB, ML
  • we focus on creating a script with dependencies
  • Frees up these hours (marked with ? is unsure):
    • Thursday 14:15-15:00 ('Formal testing framework')
    • Can be removed: BC, RB, ML
    • Thursday 15:15-15:40 ('Formal testing framework')
    • Can be removed: BC, RB, ML
    • Friday 09:00-10:00 ('Implement the project as a package')
    • Can be removed: BC, RB, ML
    • Friday 10:15-11:00 ('Implement the project as a package')
    • Can be removed: BC, RB, ML
    • Friday 13:00-13:40 ('Deployment')
      • This is about defining the dependencies and installation instructions
      • Parts can be presented the first day by giving a secure workflow
    • Is needed, BC volunteers to keep teaching
    • Add 1 extra hour on day 1
    • Friday 13:40-14:00 ('Documentation')
    • Is needed, BC volunteers to keep teaching
    • Friday 14:15-15:00 ('Documentation')
    • Is needed, BC volunteers to keep teaching

Sessions not taught:

  • 8.3 - 9 8 8 RB: 5d from [Wilson et al., 2014]: Use a symbolic debugger.
  • RB
  • 8 - 9 7 8 RB: 8a from [Wilson et al., 2014]: Use pre-merge code reviews
  • RB
  • 7.7 - 8 7 8 Runtime speed profiles
  • ML
  • 7.7 - 6 9 8 Big-O
  • ML
  • 7.3 - 8 6 8 Improve run-time speed
  • ML
  • 7.3 - 8 7 7 RB: 7b from [Wilson et al., 2014]: refactoring
  • RB

...

  • 7 - 8 6 7 Class design
  • 7 - 7 7 7 SOLID design principles

  • 7 - 6 8 7 Cybersecurity risks

  • Add in-code comments when appropriate

  • Probably more from [Wilson et al., 2014] and [Wilson et al., 2017]

    • Comment: 10 years old by now! Time to find possibly more up-to-date?

References