Hi Carol, Maxime, and Greg,
Thanks for the input. For this time we've decided to just keep it to one
weekend, partly because we are afraid of exactly what you describe: losing
people because they let other obligations get in the way :(
Very detailed metrics and great notes, Carol--thank you. If
I haven’t run a regular workshop in a while, but that was my experience as well
- roughly half of the participants in one week would show up in the next, and
roughly half of those came to weeks 3 and 4 (when we did Tuesday afternoons).
Didn’t seem to matter that each day’s material was independe
Hi all,
Some feedback from me. We have attempted to have a split workshop over
two weeks, but our experience is a large amount of "no-show" on the
second week. I would not recommend it.
--
-
Maxime Boissonneault
Analyste de calcul - Calcul Québec, Université La
Thanks, Darya, that does help. Sounds like what we have in mind. We decided
against having any sessions in the evening precisely because we're worried
about people being tired. We've also had people ask if they can just attend
e.g. the git/Github session, but I think we want to do what we can to
Hi David,
I ran a 4 x 3 hours session workshop after hours a few years ago, to try to
accomodate students who couldn't make the standard 2x full days format.
The hardest challenge to deal with was people not showing up/not being able
to make all 4 sessions, and losing people who didn't "get" what
In fact today we just started our first "split" workshop, covering a
standard SC Python track along two weeks. I usually set up two days
workshops, but noticed that some people was reluctant to attend for two
full days in a row, and decided to split the lessons once in a while.
Far more people tha
Hi Raniere, Meredith, and Maneesha,
Okay, good to know (a) I'm not the only one who felt weird about this and (b)
other people have experimented with a more spread out version and reported
back. Looks like they address some of the exact questions we had. Thanks!
We definitely plan to include al
Hi David,
Vanderbilt's doing something similar. We're planning on having a 1.5 mo long
Software Carpentry workshop hosted every Friday. We'll use the core, required
curriculum (Shell, Git, Python or R) and the lesson on SQL. Shell and Git will
each take one day, and Python and SQL will be brok
