"Congratulations on making it to Week 4. Over the last three weeks, you’ve learned how to assign variables, visualize data, and simulate complex motion step-by-step. Today, you stop being my students and start being the architects of your own classrooms. Your goal today is to take one physics concept—one that is usually hard to visualize—and build a tool that makes it crystal clear."
"A good virtual lab is a conversation between you and your future student. Start with a Text Cell that 'hooks' them. If you’re doing braking distance, ask them about road safety. Then, provide the 'Engine.' This is your code cell. Make sure your variables are clearly labeled so the student knows where to change the 'Mass' or 'Friction.' Finally, your graph should be the 'Reward'—the visual proof of their experiment."
"I’m grading you on **Pedagogy** as much as **Code**. I want to see that you’ve thought about the user. Is your code commented? If a 10th-grader looks at your loop, will they understand that `v = v + a*dt` is how the speed increases? Use the rubric on the screen as your checklist."
"Use your AI partner today to build the skeleton of your project. But remember—the AI is just a junior developer. It might forget to label the X-axis or it might use a time-step that is too large. You are the Architect. You must refine the code until it’s a professional teaching tool."
"Before you hit 'Submit,' do a 'Clean Run.' Go to the menu and select 'Restart and Run All.' This ensures that your notebook doesn't rely on some hidden variable you created an hour ago. If it runs smoothly from top to bottom, it’s ready for your students."