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

lesson timings too short + no exercise timings #452

Open
marwahaha opened this Issue Jan 19, 2018 · 3 comments

Comments

Projects
None yet
6 participants
@marwahaha
Contributor

marwahaha commented Jan 19, 2018

I'd rather this be a discussion vs make a PR.

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:

Lesson Content timing (min) Exercises timing (min)
01-numpy 60-75 30
02-loop 30 15
03-lists 30 15-30
04-files 20 10-20 (I rarely teach this bit)
05-cond 30 20
06-func 30 20
07-errors 30 20? (I don't always use the examples here; I often teach errors as I/learners make mistakes)
08-defensive 30 20? (I rarely get here)
09-debugging 10 5 (I try not to lecture too much)
10-cmdline 30 20 (I rarely get here; when I do I don't often use these examples)
@annefou

This comment has been minimized.

Collaborator

annefou commented Mar 3, 2018

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.

@caseyyoungflesh

This comment has been minimized.

Contributor

caseyyoungflesh commented Jun 17, 2018

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)

@maxim-belkin

This comment has been minimized.

Collaborator

maxim-belkin commented Jun 18, 2018

Thanks @marwahaha.
Let's do what you've suggested, @caseyyoungflesh.
Feel free to submit a PR.
In the meantime, I'll work on breaking down the first episode.

maxim-belkin added a commit that referenced this issue Jun 25, 2018

01-numpy.md: update time estimates
Pull Request: #557

Related to: #452
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment