Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update to instructor notes #361

Merged
merged 10 commits into from
May 28, 2024
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -69,11 +69,11 @@ This indicates that the maintainers will welcome pull requests fixing such issue

Current maintainers of this lesson (in alphabetical order) are:

* [Matthew Bluteau][matthew-bluteau]
* [Matthew Bluteau][matthew-bluteau] - Lead Maintainer for the period 1 May 2024 - 30 April 2024
* [Steve Crouch][steve-crouch]
* [Kamilla Kopec-Harding][kamilla-kopec-harding]
* [Doug Lowe][doug-lowe]
* [Aleksandra Nenadic][aleksandra-nenadic] (lead Maintainer for the period 1 October 2023 - 31 March 2024)
* [Aleksandra Nenadic][aleksandra-nenadic]

The maintainer team aims to meet at 11:00 UK time (BST or GMT) on the fourth Wednesday each month. The meetings alternate between operations meetings and co-working sprints.
Meeting notes are kept in the [Google doc](https://docs.google.com/document/d/1-SvoY_2GvlQgJnu8zfr6VnU7sev_iWZAIwBUywNSfWE/edit#).
Expand Down
1 change: 0 additions & 1 deletion _config.yml
Original file line number Diff line number Diff line change
Expand Up @@ -93,7 +93,6 @@ extras_order:
- guide
- common-issues
- discuss
- vscode
- software-architecture-extra
- programming-paradigms
- procedural-programming
Expand Down
22 changes: 12 additions & 10 deletions _extras/guide.md
Original file line number Diff line number Diff line change
Expand Up @@ -34,16 +34,16 @@ The course has been separated into 5 sections:

- Section 1: Setting Up Environment For Collaborative Code Development
- Section 2: Ensuring Correctness of Software at Scale
- Section 3: Developing Software to Meet Requirements
- Section 3: Software Development as a Process
- Section 4: Collaborative Software Development for Reuse
- Section 5: Improving and Managing Software Over Its Lifetime

Each section can be approximately delivered in a half-day (e.g. try to allow 4 hours per section).
Each section can be approximately delivered in a half-day but even better if you can allow 1 day per section.

## Course Delivery
The course is intended primarily for self-learning
but other modes of delivery are possible
(e.g. mixing in elements of instructor-led coding-along).
but other modes of delivery have been used successfully
(e.g. fully instructor-led code-along mode or mixing in elements of instructor-led with self-work).
The way the course has been delivered so far is that
students are organised in small groups from the outset
and initially work individually through the material.
Expand All @@ -61,15 +61,15 @@ The course can be delivered online or in-person.
A good ratio is 4-6 learners to 1 helper.
If you have a smaller number of helpers than groups -
helpers can roam around to make sure groups are making progress.
While this course can be live-coded by an instructor as well (in the earlier stages),
While this course can be live-coded by an instructor as well,
we felt that intermediate-level learners are capable of
going through the material on their own at a reasonable speed
and would not require to code-along to the same extent as novice learners.
In later stages, exercises require participants to develop code more individually
so they can review and comment on each other's code,
so the codes need to be sufficiently different for these exercises to be effective.
Having an instructor live-code would make everyone have exactly the same code on their machines
and would not have the same effect.
For instrctor-led mode of delivery, you can have an instructor live-code these group exercises
anenadic marked this conversation as resolved.
Show resolved Hide resolved
after learner have been given a chance to work on them as a team.
anenadic marked this conversation as resolved.
Show resolved Hide resolved

A workshop kicks off with everyone together at the start of each day.
One of course leads/helpers provides workshop introduction
Expand All @@ -79,17 +79,19 @@ to explain what the students will be learning and doing on that particular day.
After that, participants are split into groups
and go through the materials for that day on their own with helpers on hand.
At the end of each section, all reconvene for a joint Q&A session, feedback and wrap-up.
If participants have not finished all exercises for a section,
If participants have not finished all exercises for a section (in "self-learning with helpers" mode),
they are asked to finish them off before the next section starts
to make sure everyone is in sync as much as possible and are working on similar things
(though students will inevitably cover the material at different speeds).
This synchronisation becomes particularly important for later workshop stages
when students start with group exercises.

### Helpers Roles and Responsibilities
At the workshop, everyone in the training team is a helper.
At the workshop, "self-learning with helpers" mode everyone in the training team is a helper and
anenadic marked this conversation as resolved.
Show resolved Hide resolved
there are no insturctors per se.
anenadic marked this conversation as resolved.
Show resolved Hide resolved
You may have more experienced helpers delivering introductions to the workshop and sections.
Contact the course authors for intro slides you can reuse.
Contact the course authors for the section intro slides you can reuse and you can also find slides for each
anenadic marked this conversation as resolved.
Show resolved Hide resolved
section in the course repository (for intructor-led delivery mode).
anenadic marked this conversation as resolved.
Show resolved Hide resolved

Roles and responsibilities of helpers include:

Expand Down
Loading