Skip to content

Commit

Permalink
Merge pull request #14 from manuGil/review
Browse files Browse the repository at this point in the history
Refine schedule.md for clarity and consistency in lesson delivery and…
  • Loading branch information
manuGil authored Sep 27, 2024
2 parents 336e34e + 1a8cd69 commit 2090a5d
Showing 1 changed file with 9 additions and 6 deletions.
15 changes: 9 additions & 6 deletions gitcodev/schedule.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@
The course consists of four lessons, and a lesson per day is a good way to deliver the content. Our experience has shown that participants prefer four consecutive days. However, adapting the schedule to different audiences is a very reasonable approach.

## Lessons
Lessons are organized so that participants are gradually introduced to the content. The content of subsequent lessons depends on previous lessons; therefore, we discourage the change of the lesson. Refer to [our teaching approach](teaching-approach) to learn why the order of the lessons matters in this course.
Lessons are organized so that participants are gradually introduced to the content. The content of subsequent lessons depends on previous lessons; therefore, we discourage changing the order of the lessons. Refer to [our teaching approach](teaching-approach) to learn why the order of the lessons matters in this course.

| Lessons | Day |
|:--------------|:---------|
Expand All @@ -12,11 +12,14 @@ Lessons are organized so that participants are gradually introduced to the conte
| Lesson 4 | Day 4 |

## Sessions
Each lesson has been designed to be delivered in four and a half-hour sessions.
The content of each lesson has been optimized to provide the lesson in a way that reduces the cognitive overload of
the participants. We recommend delivering each lesson following the following timetable.
A lesson has been designe to be delivered in one session. In our experience, the legth of a session should be at least four hours, but we do not recommend to exceed four and a half hours. The content of each lesson has been optimized to provide the lesson in a way that reduces the cognitive overload of the participants. We recommend delivering each lesson following the following timetable.


| 00:00 | 01:00 | 01:10 | 02:00 | 02:20 | 03:10 | 03:20 | 04:10 | 04:30 |
| 00:00 | 00:50 | 01:00 | 01:50 | 02:10 | 03:00 | 03:10 | 04:00 | 04:10 |
|:-------|:------|:------|:------|:------|:------|:------|:------|:------|
| Lesson 60' | **Break 10'** | Lesson 50' | **Break 20'** | Lesson 60' | **Break 10'** | Lesson 50'| **Wrap-up 10'** | Closure |
| Teaching 50' | **Break 10'** | Teaching 50' | **Break 20'** | Teaching 50' | **Break 10'** | Teaching 50'| **Wrap-up 10'** | Closure |


`````{important}
If a session must be longer what it is suggested above, we recommend to extend the *teaching* times up to 60 minutes, but maintaining the duration and frequency of *breaks*.
`````

0 comments on commit 2090a5d

Please sign in to comment.