Suggest rule what is and what is not course content

[richelbilderbeek]

Currently, we struggle with what to yes/no put in the course materials.

Here I suggest to agree on a rule for this, to help us decide on what to keep/remove. Post your one or more suggested rules below, we'll vote for them after all suggestions have been collected :-)

[richelbilderbeek]

My suggest rule (let's call it Rule 1) is:

• Only discuss theory that ...
  • is (and can be) checked by an exercise
  • is needed for the shared project
• When in doubt, remove.
• If there are two ways to do something, pick the one way which involves the least amount of new concepts.

Green flags, i.e. it is a likely candidate to be kept:

• 'You need this'

Red flags, i.e. it is a likely candidate to be removed:

• 'maybe this is useful'
• 'if you have the time, you may want to take a look at ...'

[richelbilderbeek]

Here is Rule 2, which I put in the meeting notes:

• Only what is used by the student project is course content. The student project is a piece of maintainable and tested Python code

[richelbilderbeek]

BCs suggestion:

• Overview of tools, workflow and formalisms kept but shorten.
• all discussions are exercises and testable understanding should be related to
  • academians
  • make effective programming development in projects
  • make software
    • reusable
    • understandable/-stood
    • installable

[richelbilderbeek]

The rule voted for at the meeting of 20240911:

Only what is used by the student project is course content, with alternatives relevant to academics provided in lecture (or rest of extra material) to what we do