Learning Intention
Today I will practice reviewing code and design choices, and learn how feedback improves digital prototypes.
✅ Success Criteria
I can give specific, constructive feedback about my partner’s site or design choices and use that input to improve my own project.
🌍 Why Are We Learning This?
Feedback helps us notice blind spots, improve teamwork, and make stronger digital products. Sharing and critiquing prototypes is a vital skill in tech careers.
🧠 Warm-Up – Tech Journal Prompt
💡 “How does it feel to have someone review your work? What makes feedback helpful — or unhelpful?”
📚 Word of the Day
Refactor
Definition: To improve the structure and clarity of code without changing what it does.
Sentence: "We refactored our HTML so that it was easier to read and fix."
Why it matters: Refactoring makes your code more efficient, less buggy, and easier for others (or you in the future) to use.
📣 Formative Lecture & Guided Discussion
Modeling effective peer review: Tools/criteria for giving helpful feedback.
Demo: How to use “Code Tag” and commenting features in your platform (SkillStruck, Replit, or Notion).
Discuss: What’s the difference between style feedback and logic/code feedback?
✅ CFU #1: “Which part of your partner’s project was the strongest? How could they improve?”