Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add general instructor notes #42

Open
13 tasks
kaijagahm opened this issue Aug 29, 2024 · 0 comments
Open
13 tasks

Add general instructor notes #42

kaijagahm opened this issue Aug 29, 2024 · 0 comments
Labels
type:documentation Improvements or additions to documentation

Comments

@kaijagahm
Copy link
Collaborator

kaijagahm commented Aug 29, 2024

  • In instructor notes:
  • add suggestion to use the ether pad for asking questions/interacting with students/collaborative note-taking?
  • add note about clearly stating LOs up front/introduce each LO as you start a new section and clearly show how the example or exercise addresses the LO.
  • Write something about the concept of teaching using live-coding and to tell students how to follow-along (aka they should type along with the instructor, no copy-pasting, we can provide the script at the end of the lesson but they should really create their own script, determine how they should signal if they get stuck or whether the instructor is going to fast, how to ask for help, etc.)
  • Clarify when/where we suggest asking interactive questions, but left up to the instructor
  • e.g., instead of talking through examples, start live-coding. Maybe start on the exercises together?
  • comment on starting to work in R earlier
  • XOR: should we have a dummy script for the instructors as a guide for the live-coding? As in, here is what the script would end up looking like at the end of the lesson, but you should be writing each step as you go…
  • KG: just have examples explicitly written out in the lesson, and then the instructor can type those in as they go.
  • should we add stuff about making sure you share your screen at all times whether on etherpad or R studio, making sure the lettering is large enough, making sure your do not disturb is turned on… it’s all stuff covered in instructor training but maybe we can just have a little checklist? I don’t know…
  • Clearly suggest where it would be good to have check-ins with the learners.
  • add when good areas for group-work
  • feedback about having more space to go through simple questions as a class: e.g., how do we find the same error? does the same error mean it’s a reproducible ex? what can be done in case of more vague errors? “Logically stepping through could help express this a bit more. Reinforce prior sections in identifying error messages”
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

1 participant