Hi all, I'm sure this has been discussed before but I don't seem to be able to find the right set of search terms.
How do people feel about splitting a Software Carpentry workshop up into two consecutive weekends so that it's (roughly) four four-hour days total? Is that a major no-no? We had our first workshop in September and definitely lost people on the second day, and felt like it dragged near the end of each day. Now we are planning our second workshop, and this time it will include undergrads. That rules out a big chunk of the week (because of conflicts with undergrad classes), and the likelihood that they will stay for an entire eight hour session. In our discussion so far, we've considered: - some sort of worksheet that would let people practice what they've learned between the two weekends, and - a review/question-and-answer section at the beginning of the second weekend to help people ease back into the material. Any advice and feedback is welcome. Thanks, David David Nicholson, Ph.D. nickledave.github.io https://github.com/NickleDave Prinz lab <http://www.biology.emory.edu/research/Prinz/>, Emory University, Atlanta, GA, USA https://data-science-for-scientists-atl.github.io/ ------------------------------------------ The Carpentries: discuss Permalink: https://carpentries.topicbox.com/groups/discuss/T1e9023d7a45042e7-M8f63fa36af3949f5e366aa24 Delivery options: https://carpentries.topicbox.com/groups/discuss/subscription
