Hi all, Thank you very much for the discussion and tips. I agree that Git day2/evening is a no go, and we will discuss internally whether doing it on day1/eve or on day2/morning.
I always do a "three good - three bad things" survey for the whole workshop as the last task in the workshop. I may add this single specific question there: whatever we do, asking whether they would rather do it the other way around. Should we do it, I'll report back. Thanks all for the feedback, Iñigo On Tue, 27 Feb 2018 17:43:13 +0000 "Hilgert, Uwe K K - (hilgert)" <hilg...@email.arizona.edu> wrote: > Out of 9 general SWC workshops we organized at the University of > Arizona since 2015, we taught - with good success - the last 5 > workshops by integrating GitHub/git early on into the bash section > and by utilizing them frequently during the entire run of each 2-day > workshop. > > Thank you, > Uwe > > > ------------------------------------------------------------------------ > Uwe Hilgert, Ph.D. > > Associate Research Professor > Director of Industry Relations, Workforce Development & STEM Training > BIO5 Institute (http://www.bio5.org), The University of Arizona > (http://www.arizona.edu) O 520-626-1367 | F 520-626-4824 > > From: Discuss [mailto:discuss-boun...@lists.software-carpentry.org] > On Behalf Of April Wright Sent: Tuesday, February 27, 2018 9:55 AM > To: Maneesha Sane <manee...@carpentries.org> > Cc: discuss@lists.software-carpentry.org > Subject: Re: [Discuss] Default git/python lesson order > > I agree with Maneesha about not introducing git in the second > afternoon. Git can be challenging, and hard to understand in terms of > the motivation for use. > > If you do a second Python/R session in the second afternoon, you > could put a solution to one of the challenges in the workshop repo, > and have the learners pull it to compare with their solution. Or add > and commit their functions, and roll back a change when they make a > mistake. That way, you can reinforce the concepts as you go in the > context of something semi-familiar. > > April > > --------- > Assistant Professor, Southeastern Louisiana University > Biology Department > 403 Biology Building > 2400 N. Oak St > Hammond, LA. 70402 > 512.940.5761 > https://paleantology.com/the-wright-lab/<http://wrightaprilm.github.io/pages/about_me.html> > > On Tue, Feb 27, 2018 at 10:26 AM, Maneesha Sane > <manee...@carpentries.org<mailto:manee...@carpentries.org>> wrote: I > agree, I don't see a big difference in the two schedules Iñigo > proposed. > > I've seen these both work well because by the end of Day 2, > instructors and learners alike are quite tired making it harder to > introduce an entirely new concept like git that afternoon. Instead > they'll do more R or Python, which learners started to explore > before. So they have some familiarity with it. So I'd recommend > against doing git the afternoon of day 2. I also think it is > important to always begin with shell, because familiarity with using > the command line is important to learning everything else. > > That said, we do prescribe that all three topics (shell, git, > programming language) be taught in one workshop. How you break them > out is up to the hosts and instructors - we do not prescribe that > part. > > Thanks, Iñigo, for bringing up this discussion. It's something > important for instructors to think about as they plan their workshops. > > Best, > > Maneesha > > > > > > > > > > > > Maneesha Sane > Program Manager > Instructor and Trainer > Software Carpentry: https://software-carpentry.org/ > Data Carpentry: http://www.datacarpentry.org/ > > On Tue, Feb 27, 2018 at 11:01 AM, Amy E. Hodge > <amyho...@stanford.edu<mailto:amyho...@stanford.edu>> wrote: I have > always seen this taught as shell/python(I) on day 1 and > python(II)/git on day two. But I think this was typically because one > instructor was doing all of the python lessons and the instructors > preferred to each do a half day instead of each doing a full day. If > the instructors are splitting up the python lesson, they might prefer > to have it all on one day so they each get a half day. Tired > instructors may have as big an impact on the workshop as the order of > the content for the learners. > > ~ Amy > > Amy E. Hodge, PhD > Science Data Librarian > amyho...@stanford.edu<mailto:amyho...@stanford.edu> > 650.556.5194<tel:(650)%20556-5194> > [cid:image001.png@01D3AFB5.87356080] > orcid.org/0000-0002-5902-3077<https://orcid.org/0000-0002-5902-3077> > > Data Management Services > Branner Earth Sciences Library, 212 Mitchell > 397 Panama Mall; MC 2211 > Stanford University > Stanford, CA 94305 > > From: Discuss > <discuss-boun...@lists.software-carpentry.org<mailto:discuss-boun...@lists.software-carpentry.org>> > on behalf of Raniere Silva > <rani...@rgaiacs.com<mailto:rani...@rgaiacs.com>> Date: Tuesday, > February 27, 2018 at 6:17 AM To: Inigo Aldazabal Mensa > <inigo_aldaza...@ehu.eus<mailto:inigo_aldaza...@ehu.eus>> Cc: > "discuss@lists.software-carpentry.org<mailto:discuss@lists.software-carpentry.org>" > <discuss@lists.software-carpentry.org<mailto:discuss@lists.software-carpentry.org>> > Subject: Re: [Discuss] Default git/python lesson order > > Software Carpentry doesn't enforce a order for the lesson be taught. > You must teach Bash, Git and best practices in one language (normally > Python or R). The order can be adjusted based on the audience. I > taught in both scenarios that you described and I can't say that I > noticed a big difference for the learners. > > Cheers, > Raniere > > _______________________________________________ > Discuss mailing list > Discuss@lists.software-carpentry.org<mailto:Discuss@lists.software-carpentry.org> > http://lists.software-carpentry.org/listinfo/discuss > > > _______________________________________________ > Discuss mailing list > Discuss@lists.software-carpentry.org<mailto:Discuss@lists.software-carpentry.org> > http://lists.software-carpentry.org/listinfo/discuss > _______________________________________________ Discuss mailing list Discuss@lists.software-carpentry.org http://lists.software-carpentry.org/listinfo/discuss
