You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The 01- lesson, with exercises, commonly takes the first half of an afternoon (especially since there is no intro to variables, data types, etc.; learners are "thrown in the deep end"). It is only with careful skipping of certain parts can I fit a number of lessons in a 3-hour session. Even across two days, there is a massive amount of material to cover, which the timings (in my opinion) underestimated.
Here is my (conservative overestimate) timings of bits of the workshop, based on my instructing/co-instructing:
It's true that the timing is quite approximative and the effective time will depend on the audience. And you are right, we often have to skip episodes or exercises and even though rarely reach the end of the lesson.
Many of the Software Carpentry lessons are too long, and it is not always clear, especially to new Instructors, what are the essential elements of the lessons that need to be taught.
The Carpentries are taking this issue very seriously and task force is being assembled to identify these elements. If you wish to participate or discuss this issue further, let us know.
I would second this. Lesson 01 is substantially longer than noted (60+ mins vs. 30 min; exercises ??? min vs. 0 min). While shortening or breaking this section up might be an option, I might suggest changing the expected time to start (low effort, partial solution)