Community Data Science Workshops (Spring 2014)/Reflections: Difference between revisions
Content added Content deleted
imported>Mako |
imported>Mako |
||
Line 153: | 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. |
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. |
||
== |
== General Feedback == |
||
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. |
|||
we want to focus on getting people more toward independence. |
|||
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. |
|||
people didn't quite make it all the way |
|||
our final session seemed to let out a little bit on a low point int he class |
|||
* 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). |
|||
one suggestion is to have a final session with no lecture or curriculum. people can come and mentors will be with them to work o n projects. |
|||
⚫ | |||
of course, we want everybody to come so we shoudl have a set of "random" projects for folks that don't have them already |
|||
⚫ | |||
* logistic observations |
|||
** budget |
|||
* 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). |
|||
⚫ | |||
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 |
For lunch we spent between $400 (pizza), $360 (less pizza), and $600 |
||
Line 181: | Line 194: | ||
If you had a toal budget would be in the order of $2000-2500, I think |
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. |
you could easily do a similar 3.5 day-long sessions. |
||
Things we sould do differently |
|||
spacing between sessions too much |
|||
- every other week? |
|||
⚫ | |||
⚫ | |||
maybe include some spot where we can talk for 10-15 minutes bout how to use documentation |
|||
more windows experienced mentors |
|||
challenge going to the right directory . understanding about the path and the idea that files/datasets need to be local to the place the script is run. that was unclear |
|||
⚫ | |||
things to teach: |
|||
- debugging |
|||
⚫ | |||
- troubleshooting and looking at stackexchange |