Instructor training course preparation

# Instructor training course preparation ###### tags: `Training` # Participants Sabry, Radovan, Anne, Richard Workshop page: https://coderefinery.github.io/2020-11-02-instructor-training/ Course: https://coderefinery.github.io/instructor-training/ Registrations: 15 so far https://twitter.com/HPC_Guru/status/1320740458365026304 # TODO - start with zoom/hackmd mechanics (teach how to do online workshop by showing how to): is in the manual - split "welcome" into intro and "about CR" - practice teaching: includes also screen setup, readability ## What do we do differently/better - Planing, teaching material available in advance and not PDF slides - different roles (instructor, host, hackmd, ...) - Github projects board so all boxes are checked - Helper recruitment and breakout room planning - designing for this as soon as you open registration - less is more - welcome - clearly defining learning outcomes - asking for feedback, encouraging feedback - manual - screensharing - lesson templates - lesson review on github - sharing material instead of being protective ## New schedule idea ### Learning outcomes - Teach HPC carpentry lessons - Manage cognitive load of learners - Motivate them to use HPC resources instead of scaring them away - Competently use technical tools, e.g. screenshare well, don't go too fast, etc. - Place yourself into the learner's perspective (possibly everything is new) - Create own lessons - Backwards lesson design - Learner personas, clearly defining target audience - Devolping good exercises and examples - - Use collaborative workflows - git, github - network of teachers - Make it possible to consolidate material and encourage contributions (even from learners) - Run workshops - Effectively teach over online - Train helpers - Kickstart other instructors Top issues new instructors face: - Breaks are not negotiable, minimum 10 minutes. - Breakout sessions too short. Make them as long as possible, don't expect to come back for new intro, then go back. - People will accomplish less than you expect. Expect learners to be 5 times slower than you, at best! - All the other tools and stuff will go wrong. Try to not bring in a dependency when you don't need it. - Trying to accomplish too much: it's OK to cut out and adapt to the audience. Have a reserve session at the end you prepare, but are ready to skip. - Explaining how, but not why. - Running out of time to making your environment match the learner's. - Running out of time to set up good screen sharing practices (terminal history, portion of screen, remote history) in advance. - Assuming learners remember what they have already learned, or know the prerequisites. Or have stuff installed and configured. - Not managing expectations: learners think that you will accomplish everything, and feel sad when you don't. **Exercise: List the things you think can go wrong when teaching** (online? hands-on work?) ### day 1 (4 hours) (connect 10 minutes early) - 20 min **About workshop** - hackmd and zoom mechanics - overview over days 1-3 - introduction round - 30 min **Teaching philosophies** (Anne) - 15 min (main room) - 15 min (group work) - learning outcome: nobody is born as a teacher, discussing this with others helps, it's about the learner - Openness - Collaborative development - In-person strategies - Online techniques to scale to large size - 30 min **teaching style** (Sabry) - https://github.com/coderefinery/instructor-training/blob/master/content/03-teaching-style.md - carpentries - CR - concept maps - effectiveness of learning - simplicity - connect this to HPC: HPC prerequisites - clearly define learners profile (you cannot teach shell in the morning and job submission in the afternoon) - **Workshop organization and prep** (richard) (50 min) - staff training - online teaching - Our helper training - Our instructor kickstart - also let's say few words about in-person workshops - **How to teach online** - Lessons from our online teaching - **CodeRefinery collaboration network** - about coderefinery - 15 min **Collaborative lesson tools** - Carpentries template - CodeRefinery template - Development by GitHub ### "Future" episode at beginning copy to hack, encourage hackmd answers tell what CR is before making a case to get involved - project in "one sentence" - overview of a typical workshop - where are the lessons what can we motivate particiapnts? - collaborate on hpc carpentry workshops (faster, sooner, closer in culture) - who will end up teaching hpc carpenetry? - what do you need from us/somebody as support Nordic-RSE - announce meetup and conference - map - meetings collaborative workshops - ideas for more of this? (refer to discussion in last episode) biggest open problems - credit/visibility for helpers/contributors - how to promote/engage new members - we don't know how we should be in relation with Carpentries - what are we? non-profit? organization? selling services? - funding and sustainability - mention ideas: - collaboration network - do people see collaboration possibilities with CoE (not only hpc carpentry) - how to reach more people (RSH, twitch? streaming-only workshops?, recording post-processing) - scalability and marketing questions how to get involved - chat workshop feedback - is this useful? remove pictures at the bottom of "future" and re-add later ## static site template demo - Find the template we want to use - generate from template - Fix site metadata / title/etc - Show that it renders properly on gh-pages - make a pull request - create a new episode page - make a pull request - -