Supporting reflection in introductory computer science
Proceedings of the thirty-first SIGCSE technical symposium on Computer science education
Patterns in learning to program: an experiment?
ACE '04 Proceedings of the Sixth Australasian Conference on Computing Education - Volume 30
Students' alternative standards for correctness
Proceedings of the first international workshop on Computing education research
Why students drop out CS1 course?
Proceedings of the second international workshop on Computing education research
CS1 students speak: advice for students by students
Proceedings of the 40th ACM technical symposium on Computer science education
Also "your" job to learn!: helping students to reflect on their learning progress
Journal of Computing Sciences in Colleges
How we teach impacts student learning: peer instruction vs. lecture in CS0
Proceeding of the 44th ACM technical symposium on Computer science education
Reading mobile games throughout the curriculum
Proceeding of the 44th ACM technical symposium on Computer science education
Using POGIL to help students learn to program
ACM Transactions on Computing Education (TOCE) - Special Issue on Alternatives to Lecture in the Computer Science Classroom
Proceedings of the 13th Koli Calling International Conference on Computing Education Research
Hi-index | 0.00 |
Expertise is developed through both a) self-reflection and b) making useful plans for improvement [3, 10]. Traditional novice-level programming assignments require neither of these skills to be used. Could we get students to think about improving their software development processes? What areas would they identify as needing improvement? Could they write effective plans for themselves? In this experience report, we analyze the results of an intervention with 236 CS1.5 students asking them to do these activities. We find that they most commonly make improvements in planning, compared to coding and testing. Additionally, over half of the plans they make are so vague as to be of little use in helping students identify if they have, in fact, improved. Finally, we asked students at the end of the term to reflect on how their experiences with programming assignments changed over the term. We discuss our results in light of how instructors can focus instruction to help students become more meta-cognitive about their own software development processes.