110 likes | 219 Vues
This guide outlines the key differences between effective and ineffective reflection papers in computer science courses. Good reflection papers connect course topics to personal experiences, employ a first-person, conversational tone, and are selective in their focus. They highlight “ah-ha!” moments and provide insights that enhance understanding. In contrast, bad reflection papers simply recite course material, lack personal engagement, are overly formal, and often contain grammatical errors. Recognizing these distinctions can improve student reflection and enhance course design.
E N D
Good vs. Bad Reflection Papers in COMP courses Todd A. Whittaker whittakt@franklin.edu
Good Reflection Papers… • Connected topics both within and outside of the course material • Prior courses • Work experience • Modules in course
Good Reflection Papers… • Were written in first person singular • Personal • Conversational • Reflective • Casual • Easy to read
Good Reflection Papers… • Were selective in their topics • “Ah-ha!” moments • In the moment • One or two key ideas per week
Good Reflection Papers… • Contained examples or quoted the key points or textbook • Interaction with material • Added insight to knowledge
Good Reflection Papers… • Identified both good and bad parts about the course • Helps with course design • Identifies weak spots • Builds on strengths
Bad Reflection Papers… • Were a recitation of the course material • “This week we learned…” • Tried to teach the teacher
Bad Reflection Papers… • Were formally written • Third person or first person plural • Accompanied recitation of material
Bad Reflection Papers… • Tried to cover too much • Seemed to want to convince the instructor that they learned something.
Bad Reflection Papers… • Contained too many grammatical and spelling errors • I just stopped reading
Bad Reflection Papers… • Were way too long • 3 to 5 pages was sufficient • Many were 10 or more