Anonymous user
Community Data Science Workshops (Spring 2014)/Reflections: Difference between revisions
Community Data Science Workshops (Spring 2014)/Reflections (view source)
Revision as of 23:15, 10 July 2014
, 9 years ago→final thoughts
imported>Mako |
imported>Mako |
||
Line 153:
The challenge with MatPlotLib was mostly focused on installation which took an enormous amount of time. In the future, we will use Anaconda which we hope will address these issues because Anaconda includes MatPlotLib.
==
Our goal was get learners as close to independence as possible but we felt that most learners didn't make it all the way. In a sense, our our final session seemed to let out a little bit on a low point int he class in the sense that many user had learned enough that they were able to work but not enough that they were not struggling enormously in the process.
One suggestion is to add an additionial optional session with no lecture or planned projects. Learners could come and mentors will be with them to work on ''their'' projects. Of course, we want everybody to be able to come so we should also create a set of "random" projects for folks that don't have them.
* The spacing between sessions too much. In part, this was due to the fact that we were creating curriculum as we went. Next time, we will try to do the sessions every other week (e.g., 3 sesions in 5 weeks).
* The breaks for lunch were a bit too long. We took 1 hours breaks but 45 minutes
* We did not have enough mentors with experience using Python in Windows. We had many skilled GNU/Linux users and ''zero'' students running GNU/Linux. Most of the mentors used Mac OSX and most of the learners ran Windows.
* Although we did not use it as a recruitment or selection criteria, a majority of the participants in the session were women. Although we had a mix, the fact that most of our mentors were male and most of he mentors were female set up a strange dynamic. If we expect to have a similar ratio in the future, we should recruit female mentors and, in particular, attract women to lead the afternoon sessions (all of the afternoon session leaders were male).
* The SWC-style sticky notes worked
We might also want to spend time devoting more time explicitly to teaching:
* Debugging code
* Troubleshooting and looking at StackExchange for answers to programming questions.
=== Budget ===
For lunch we spent between $400 (pizza), $360 (less pizza), and $600
Line 181 ⟶ 194:
If you had a toal budget would be in the order of $2000-2500, I think
you could easily do a similar 3.5 day-long sessions.
▲breaks for lunch were a bit too long. 45 minutes shoudl be enough. folks were interested in getting back in action. food was simple and always there on time so we could have jsut run with this
▲the general structure of the entire thing was not as clear as it might be or could be. this was at least in part because the details of what we would teach int he later sesions were not done when we started
▲sticky notes worked super well but sort of gained less value as we went along
▲- reading documentation
| |||