Walkthrough of workshop, focusing on the following:
Git integration
What concepts will be performed when?
Will there be formative assessments? If so, when and what?
Formative assessments
When they will be performed?
What is the formative assessment?
Scheduling
Day 1
What is the latest time to get started with module 1?
What "state" should the learner's laptops be in when we start?
Day 2
What is the latest time to get started?
What "state" should the learner's laptops be in when we start?
Is there enough time for each module?
Specifically, shell/git integration.
Helpers.
Pre-workshop dinner with helpers
What do you want to tell the helpers?
Do we need checklists for each day?
Summary
Clarified that this workshop will not have a dedicated Git module. Git commit will be taught in the Shell module, and the process of making commits will be repeated thoughout the rest of the workshop.
Repeating the process of making a commit should/may be done after completing instruction of a particular concept from your concept maps.
When learners are making commits, instructors should mention or speak about data managament. Ideally, instructors should help the learners make commits such that viewing the history reinforces the idea of data management (e.g. one commit for code changes, a separate commit for data changes).
We discussed formative assessments, and slightly altered the timeline of the workshop:
Shell will have an extra hour after lunch (@MarneeDear and @thanyta stated they would only need 30 min)
@uhilgert will have 15 min talking time while Shell transitions to R.
Still planning on last half of 2nd day for capstone/"pulling it all together".
Discussed SC training, specifically, the idea that teaching is a performance art.
Pre-workshop dinner with host, instructors, and helpers next Thursday.
I have mentioned before that I had a set of scripts which I've used in the past to "conveniently break" the gap-minder data set, and they are also located in this repo
Actions
[ ] Actions
@strootman
[ ] Prepare for 15 min max Workshop intro before transitioning to Shell (Targeting 0915 start time).
[ ] Send out rough draft of workshop "final project" by COB Monday.
@uhilgert
[ ] Prepare to give 15 min talk, after the shell module concludes and before the first R module.
This will help provide time to transition between instructors.
All
[ ] Work on formative assessments.
I've created an issue for formative assessments #2 (what concept are you assessing? How are you assessing it?), and check it into some location in the workshop repo.
Dinner on Thursday
All instructors should think about their expectations from helpers, and ensure that these expectations are made clear during the dinner.
Attendees:
Agenda
Walkthrough of workshop, focusing on the following:
Summary
Clarified that this workshop will not have a dedicated Git module. Git commit will be taught in the Shell module, and the process of making commits will be repeated thoughout the rest of the workshop.
Repeating the process of making a commit should/may be done after completing instruction of a particular concept from your concept maps.
When learners are making commits, instructors should mention or speak about data managament. Ideally, instructors should help the learners make commits such that viewing the history reinforces the idea of data management (e.g. one commit for code changes, a separate commit for data changes).
We discussed formative assessments, and slightly altered the timeline of the workshop:
an extra hourafter lunch (@MarneeDear and @thanyta stated they would only need30 min)15 mintalking time while Shell transitions to R.last halfof2nd dayfor capstone/"pulling it all together".Discussed SC training, specifically, the idea that teaching is a performance art.
Pre-workshop dinner with
host,instructors, andhelpersnext Thursday.Notes
Actions
15 minmax Workshop intro before transitioning to Shell (Targeting0915start time).15 mintalk, after the shell module concludes and before the first R module.AllDinner on Thursday