2015 Post-Workshop Instructor Debriefing, Round 17

This post originally appeared on the Software Carpentry website.

The mentorship committee held their latest round of debriefing for instructors of recent workshops on Tuesday, September 1. Then, on Friday September 4th mentorship committee met for a regular bi-weekly meeting. Some comments from the committee meeting have made their way into this debriefing post.

New members on the mentoring committee

On August 22, Raniere Silva put out a call to join the mentorship committee for members to help with the debriefing session, among other things. The new members include: Rayna Harris, Christina Koch, Sue McClatchy, Mariela Perignon, Phil Rosenfield, Michael Sarahan, and Belinda Weaver.

Potential changes to the debriefing session format

Since March 2015, the debriefing sessions have served to purposes: 1) to debrief instructors of recent workshops, and 2) to give new (or even experienced) instructors an opportunity to hear how the lessons are going and get some tips. The impetus for including new instructors on the call came from a March debriefing session when some novice instructors said they would have benefited from hearing instructor experiences before doing the instruction themselves. While the dual purpose debriefing session has been working, the mentoring committee is discussing splitting the sessions. Stay tuned for more updates regarding specific mentoring opportunities for new instructors, and feel free to send your suggestions of desired resources to the mentoring subcommittee.

Capstone sessions

A few of the recent workshops included a capstone or customized session at the end. Thomas Guignard from the CU Bolder Workshop shared his notes on OpenRefine for librarians, which was based off of this lesson from the British Library. The Leeds workshop had a third day for students to find/analyze data related to environmental science (a method which Kate previewed in a previous blog post). The UNH workshop tried to incorporate a Pandas-oriented capstone using data from the learners domain; this was an excellent idea, but the lesson had to be rushed to fit into a 50 minute time frame and was therefore not as successful as the instructors hoped.

Enhancing workshops with domain-specific examples

Sometimes we get lucky and the instructors are from the same domain as the learners. When this isn't the case, we've seen that the helpers can be called on to motivate the material with domain specific examples. The Stanford workshop learners were neuroscientists, so one of the helpers demoed a Python notebook using data with which learners were familiar. The helpers also provided a "NumPy for Matlab Users" resource to help make the Matlab to Python transition a little bit easier. Likewise, the librarians in the CU Bolder Workshop are most interested in cleaning data, data wrangling, and extracting information from datasets, so it can be a challenge to tailor Software Carpentry and Data Carpentry lessons to this audience. These instructors tailored the Pandas and SQL materials to accommodate the librarian learners.

No right or wrong way: lessons materials and Etherpad

Should I give students the full set of lesson materials before or after the workshop? Should the learners or the helpers or the instructors run the Etherpad? These are hard questions to answer all options work and all have their own benefits. While some instructors worry that students will work ahead in the lessons and not pay attention, others have found that seeing the exercise instructions and full descriptions to be very helpful. Likewise, some workshops have learners that work the Etherpad with collective enthusiasm while other learners prefer to only check the Etherpad when they need help. As co-instructors Rayna and Kate code along with the main instructor and paste commands in the Etherpad, which they have found to be a very efficient and useful for the students. Whichever route you choose, just be confident in your decision.

Python reorganization

Byron Smith reorganized the flow of the Python lesson but kept many of the same details from the lessons for the UNH workshop. Additionally, one learner suggested splitting up the monolithic Jupyter Notebook into smaller pieces, which would clean up the namespace and gave learners a more manageable set of "notes". There have been many discussions on the Python lessons lately, including these blogs.

Guacamole: A Dracula-Wolfman Alternative for Git

During the UNH workshop, Ivan Gonzalez taught the Git lesson with a markdown formatted recipe for guacamole, which was an effective crowd-pleaser. Guacamole is a delicious dip that has a few staple ingredients but can really be made to one's own desire. We think this makes it a nice collaborative exercise that is relatable and engages students.

Dialogue & Discussion

Comments must follow our Code of Conduct.

Edit this page on Github