| Cool Collaborators |
Feedback |
Clarified what to submit, medium feedback |
Provide clearer written rubrics/checklists for both projects so expectations are upfront. |
| Cool Collaborators |
Hacks |
Fun, but add more hints/support. Rock-Paper-Scissors: good, but add music/how-to-change guidance. |
Add in-game hints/tutorial popups; include optional audio/music or style-change tips. |
| Cool Collaborators |
Grading |
Fair, but no rubric → unclear grading. Rock-Paper-Scissors: fair, but didn’t know criteria. |
Share detailed rubrics ahead of time; explain grading categories in class. |
| Cool Collaborators |
Lesson |
Very detailed, learned how game worked. Rock-Paper-Scissors: detailed lesson on JS classes, console, OOP. |
Keep detailed walkthroughs; supplement with recap slides/videos for review. |
| Constellators |
Lesson |
Pros = good instructions, cons = lack of clarity. Some topics missing in lessons. |
Improve clarity by including step-by-step annotated examples; cover missing topics. |
| Constellators |
Grading |
Must complete hack to show mastery. Sometimes unclear or didn’t get full points. |
Give partial credit explanations; use clearer mastery criteria. |
| Constellators |
Hacks |
Advanced, fun, but confusing directions. Wanted more examples for OOP breakout. |
Add written instructions or video demo for hacks; provide multiple starter examples. |
| Constellators |
Feedback |
Pros = received useful feedback, graded fairly. Cons = not enough examples, instructions unclear. |
Offer more sample solutions and coding templates. |
| Constellators |
Requirements |
Needed 2 foundational topics, but unclear expectations. Multiple students said unclear teaching requirements. |
Share explicit teaching requirement slides; provide model lessons. |
| Constellators |
Examples |
Wanted more varied examples (loops, streams, methods). Some found too few or too advanced. |
Expand example bank with simple → complex progression. |
