written by Eric J. Ma on 2016-06-14
I recently was asked by Dr. Hugo Bowne-Anderson (a really chill guy, who probably would insist that I drop the "Dr.") to contribute some of my thoughts on what makes a great data science workshop. Having been on both sides as an instructor and a learner, here's some of my thoughts.
What distinguishes a Data Science Workshop from a Data Science talk or lecture?
I think the distinguishing mark of a data science workshop is that the instructor will make sure that there is hands-on coding involved. The only exception to this that I have experienced was in Bang Wong's workshop on data visualization, where we did group discussion instead. In both cases, participant involvement is very important.
What are the 3 most important qualities for a great Data Science Workshop to have and the 3 most important for it to NOT have? Why (one sentence on each quality)?
My top 3 important qualities are:
It should be evident that the opposites of the above should be avoided, but I’ll put out a few ideas of common good teaching practices that might (paradoxically) be best avoided in a workshop setting:
How do you avoid losing your audience in the 1st 5 minutes?
The most important thing I learned was to keep the energy high. My verbal and body language have to show that I'm excited to share my knowledge, thrilled to meet everybody present, and eager to continue the conversation afterwards. The best instructors that I’ve seen, such as Allen Downey, do this. Following that, I think it’s important to set expectations, to clarify what will and won’t be covered.
What tools/software/resources do you use when giving a Workshop? What tools/software do you ask your attendees to use?
The topic I teach the most has been network/graph analysis fundamentals, using the NetworkX API to introduce these ideas. For this, I use Python (and the scientific Python stack, in particular), the Jupyter notebook, and git
on GitHub. I like using the RISE plugin for Jupyter, which instantly turns my code and markdown cells into slides that I can advance through. Everybody complains about font sizes being too small; RISE solves that instantly for the notebook, and I can spice up the theme by changing the CSS.
Apart from that, where possible, I try to make use of sticky notes. It’s something I picked up from my Software & Data Carpentry instructor training. Green stands for "I'm good to go!", while red stands for "I'm in need of some help."
What would you like to find in a "How to teach a great Data Science Workshop" article?
I’d like to see real feedback from students about their instructors. Nothing beats having direct feedback from the participants. I’d also like to see a list of questions that instructors should ask themselves (or have a coach-like figure ask them) after each workshop, so that we can train ourselves to focus on the most important aspects of teaching.
@article{
ericmjl-2016-how-workshop,
author = {Eric J. Ma},
title = {How to give a great Data Science Workshop},
year = {2016},
month = {06},
day = {14},
howpublished = {\url{https://ericmjl.github.io}},
journal = {Eric J. Ma's Blog},
url = {https://ericmjl.github.io/blog/2016/6/14/how-to-give-a-great-data-science-workshop},
}
I send out a newsletter with tips and tools for data scientists. Come check it out at Substack.
If you would like to sponsor the coffee that goes into making my posts, please consider GitHub Sponsors!
Finally, I do free 30-minute GenAI strategy calls for teams that are looking to leverage GenAI for maximum impact. Consider booking a call on Calendly if you're interested!