Hi April, thank you for pointing out that the core requirements for SWC are simply "structured programming in R or Python" on the website. I had always assumed that SWC requirements were more like the DC ones in that you had to cover SWC Git/mercurial, shell and python/R. perhaps I was just mistaken, but no one has ever corrected me when I have talked about this. Cheers L
Leo Browning PhD Candidate with the MacDiarmid Institute School of Chemical and Physical Sciences, Victoria University of Wellington On 18 October 2017 at 03:57, April Wright <[email protected]> wrote: > Hi Leo- > > I've been at workshops where the instructors have run some of the first DC > Python lessons in conjunction with the SWC lessons, or have run the first > couple DC and using the SWC lessons for more advanced lessons. I know I > should keep better track of how people are using the DC Python lessons (as > a maintainer of those lessons), but little substitutions are tricky to find > and track. I'm not sure about wholesale swapping. I'd love to hear from > people who are doing swapping of lesson sessions - how did it go, what did > you do, were all your needs met - if those folks want to file issues on the > DC Python repo. > > To the real question: Can you do that and call it SWC? I don't know the > answer to that. This discussion came up a bit in some of the merger docs as > something that needs clarification. DC has the requirement that 3 lessons > in a lesson group be taught to be a DC workshop, SWC says "structured > programming in R or Python". To me, teaching the DC lesson would meet that > requirement. We go over all the things that SWC lessons typically get to > (iteration, storing data in variables, multiple files), but the tools are > different and the context is different. A lot of SWC workshops don't get > all the way to debugging or command line programs, but these two lessons > could be run after the DC lessons. Hopefully someone else can weigh in and > we can clarify this going forward. > > --a > > > On Mon, Oct 16, 2017 at 10:00 PM, Leo Browning <[email protected]> > wrote: > >> Hi all, >> >> I'm new to the mailing list, so please let me know if there is anything I >> should change about the way I am posting. >> >> I would like to table the idea of using DC's python for ecology module in >> place of SWC's Python module in a SWC workshop. From what I understand the >> only reason not to is that the curriculum for SWC is fixed. >> >> I have found the DC Python lesson to be more relevant and applicable to >> learners, giving them the tools that they need to be able to work with >> data, rather than spending a large amount of time on general programming >> concepts that they would pick up along the way as the SWC Python lesson >> does. >> >> We are considering dropping the SWC branding and running the most >> applicable lessons, but i am reluctant to do so as I view the SWC pedagogy >> as excellent in general. Rather, I would like to hear from the community as >> to why there is this restriction, to better inform our decision regarding >> workshop content. >> >> Regards >> >> Leo Browning >> PhD Candidate with the MacDiarmid Institute >> School of Chemical and Physical Sciences, >> Victoria University of Wellington >> >> >> >> _______________________________________________ >> Discuss mailing list >> [email protected] >> http://lists.software-carpentry.org/listinfo/discuss >> > >
_______________________________________________ Discuss mailing list [email protected] http://lists.software-carpentry.org/listinfo/discuss
