Hi there I am currently teaching a course on "Introduction to computing at SANBI" that is largely based on Software Carpentry materials and techniques but spread over a week of mornings (course site here: http://pvanheus.github.io/computing_sanbi_032016/). The class size is very small (6 people) as this is aimed at incoming postgraduate students in our lab (I plan to repeat the course in the second half of the year for those who join us later in the year).
As part of this course I've created the start of an extra section for the shell lesson on "executable scripts and the PATH": http://pvanheus.github.io/shell-novice/07-executables.html (repo: https://github.com/pvanheus/shell-novice/blob/gh-pages/07-executables.md) It still needs exercises but I'm putting it out there for re-use and discussion. My initial impression (confirming previous teaching experience) is that the conceptual shift from "I can save my shell commands in a script" to "I can run my script as a command" is difficult because there are 3 distinction concepts - permissions, hash bang lines and the PATH - that need to be understood in rapid succession. As a result I'm thinking of splitting the lesson and introducing the concepts independently. I also assume that I have more time than a Software Carpentry 2 day workshop would allow. Peter
_______________________________________________ Discuss mailing list [email protected] http://lists.software-carpentry.org/mailman/listinfo/discuss_lists.software-carpentry.org
