3:22pm
+ Good job repeating the question for the video/remotes
+ Good job modeling good great git workflow!
+ I love your tasks for the students on the whiteboard ("How did the coder solve the problem? Did the coder get stuck? What did the coder do that I will now do?")
- ...BUT, they aren't objectives. Objectives are the way you want the students to be changed, not what you want them to do. Objectives for those might be "Identify 2 or more ways to solve programming problems", or "Commit to changing one coding behavior."
+ Doing a great job narrating your thought process
- Rather than batch all of the questions and ratio at the end, do it after each test. That gives you a chance to get them thinking at a higher level in subsequent tests.
+ "I need to make sure this runs" Yes!
+ Modeling culture of error
- You're working much harder than they are. How could get them to reflect more explicitly during this? Think of "What do _you_ think is going to happen when I run this? Who thinks the test will pass? Why?"
+ Good red-green-refactor modeling
- I would definitely refactor out those 6 temporary variables you have
3:35