I put together something like that, but the workshop was explicitly for people who wanted to learn to use a specific piece of research software. Since that software is really hard to use with knowledge of shell, git, and a scripting language, it worked out really well. There were no questions about why the material was relevant and it seemed to keep everyone motivated. But that was a group of people who specifically wanted to learn a specific research workflow. I imagine the challenge in general would be finding an example that can be used to tie everything together that would seem relatable to all of the learners.
Here's the website for the workshop: http://emilydolson.github.io/2015-10-17-avida/ Cheers, - Emily On Sat, Aug 20, 2016, 11:41 AM Bennet Fauber <[email protected]> wrote: > Jon, > > Yes, I have had similar thoughts, and I even tried to get one or more > components tied together. > > The hardest problem, with respect to the standard SWC list, is that > they are designed to be a smorgasbord, or dim sum, if you prefer, and > so each needs to stand on its own. If you have the luxury to adapt > the materials to more specific circumstances, I think you and your > learners will benefit from a more consistent and coherent theme or > task being present throughout the workshop. > > -- bennet > > > > On Sat, Aug 20, 2016 at 10:56 AM, Jon Pipitone <[email protected]> wrote: > > Hi all, > > > > A few of us at the Centre for Addiction and Mental Health in Toronto > > have been teaching a series of Software Carpentry-like workshops[1] > > (actually some of them are exactly SWC workshops) over two weeks aimed > > more specifically at researchers in our organization. Much of what we > > teach is very introductory: what is programming, how to use the linux > > shell, a very basic intro to R focusing on statistics, a MATLAB and SPSS > > primer, using Photoshop, etc.. We do also get to a few more advanced > > topics in some workshops: e.g. doing fMRI analysis in python, using a > > compute cluster. > > > > We received feedback from learners and instructors that having more > > cohesion between the lessons would be really helpful to tie things > > together (currently we have a mixture of lessons with toy examples, more > > elaborate worked examples, and some with only descriptions/powerpoint), > > but it's disjointed: there isn't a theme or example dataset running > > through the workshops. > > > > Has anyone tried creating lessons for several different topics around a > > single example scenario? E.g. using Nelle's data from the Shell > > lectures[2] to also teach R, Python, Git, etc.. How has it worked out? > > Is there anything we should be wary of as we wander down this road? > > > > Thanks! > > Jon. > > > > [1] e.g. https://camh-scwg.github.io/compucool > > [2] http://swcarpentry.github.io/shell-novice/01-intro/ > > _______________________________________________ > > Discuss mailing list > > [email protected] > > http://lists.software-carpentry.org/listinfo/discuss > _______________________________________________ > Discuss mailing list > [email protected] > http://lists.software-carpentry.org/listinfo/discuss
_______________________________________________ Discuss mailing list [email protected] http://lists.software-carpentry.org/listinfo/discuss
