Growth Reflections are informal writing about how you learn, solve problems, and respond when computational work becomes difficult. They are not technical reports or polished essays. Use specific moments from your work rather than general statements.
There is no required growth story. It is fine if something did not change, if a project went smoothly, or if you are still confused. What matters is that you reflect specifically and explain what the evidence shows.
| Reflection | Assigned | Due | Purpose |
|---|---|---|---|
| Growth Memo 1 | Tue Aug 25 | Mon Aug 31, 11:59 pm PT | Establish a useful baseline. |
| Growth Memo 2 | Tue Oct 6 | Mon Oct 19, 11:59 pm PT | Examine what has changed and what has not. |
| Growth Synthesis | Tue Nov 17 | Mon Dec 14, 11:59 pm PT | Trace the full arc of your learning. |
The prompts are guides, not a checklist. Write a connected reflection rather than answering every question mechanically. All three reflections are graded on specificity, reflection, and evidence rather than polished prose; see Grading. The AI questions are optional if you did not use AI and required if you did.
Growth Memo 1: Baseline¶
Assigned: Tue Aug 25 · Due: Mon Aug 31, 11:59 pm PT
Before the course has had much chance to change how you work, reflect on where you are now.
Describe one piece of computational, mathematical, or scientific work you are proud of. What did you do well?
How do you currently begin a coding task, and how do you decide whether your result is correct?
What do you usually do when you feel stuck or confused?
What do you expect to find most challenging in this course?
What do you hope to get out of this course? By December, what do you want to understand, be able to do, or feel more confident doing?
What will you do to help make that happen? Name two or three specific habits, choices, or sources of support you plan to use.
Describe where you are now rather than where you think you should be. This memo gives you something real to compare against later.
Growth Memo 2: Mid-semester¶
Assigned: Tue Oct 6 · Due: Mon Oct 19, 11:59 pm PT
Reread Growth Memo 1 before writing. Quote or paraphrase at least one thing you wrote there.
What are you most proud of so far? Point to a specific piece of code, test, figure, explanation, or debugging moment.
Describe a challenge you overcame. What did you try, what helped, and what did you learn? If the work went smoothly, explain what made your approach effective.
How has your approach to planning, coding, debugging, or verification changed? What has not changed?
Has your attitude toward difficulty, mistakes, asking for help, or your own abilities changed? It is fine if the answer is no.
If you used AI, explain what was helpful, what was not, and what you learned from using it as a tutor. What remained your responsibility?
What is one habit you want to strengthen during the rest of the semester?
Growth Synthesis¶
Assigned: Tue Nov 17 · Due: Mon Dec 14, 11:59 pm PT
Before writing, reread both earlier memos and skim your previous project notebooks and code. Use them as evidence rather than relying only on what you remember.
What is the overall story of your growth this semester? Ground it in two or three specific moments or pieces of work.
Where were your earlier reflections right about you? Where were they wrong?
How has your approach to computational problems, debugging, and verification changed?
What are you most proud of accomplishing?
What was your most difficult challenge, and how did you respond?
Has your attitude toward confusion, mistakes, difficult problems, or your own abilities changed? What has not changed?
If you used AI, how did your use evolve? Explain when it helped you learn, when it did not, and what you learned about using it as a tutor responsibly.
What still feels difficult or unfinished, and what practices will you carry into future work?