The final reflection is the last piece of writing in this course: one sustained look across your whole Code Journal, written in the final week. Every other entry looked at a single day. This one reads the entire record and answers the question a course can actually be measured by — what do you leave with that you did not arrive with?
Before you write
Reread the journal front to back in one sitting, with the commit history open beside it. Expect the earliest entries to feel written by somebody else. As you read, flag:
- one entry that embarrasses you a little; that is usually where the growth is buried
- one design decision you would now make differently, and what you know that you did not know then
- one review — given or received — that changed the code
- one thing you understood about a program you did not write, and how you got there
- one thing your community partner said that changed what you built
The shape
Five sections, roughly two pages, built the way Showing Growth taught: cite the earlier entry, quote your own words, then show the now.
- How my building changed. The biggest difference between what first-week you and current you can make, proven with two cited entries.
- How my deciding changed. The harder and more interesting axis. Find an early entry where you chose something without noticing you were choosing, and set it beside a decision you defended with a measurement, a test, or an argument. This is the section where Efficiency and Big-O stops being vocabulary and becomes something you use.
- How I work with other people, and their code. What you now do that you did not do at the start of the course: reading before rewriting, asking in review instead of assuming, saying “I am stuck” on the day rather than the week after. Be specific about what a teammate taught you. Be specific, too, about what you were like to work with in the first weeks, if you can bear it.
- What I left behind, and where this goes next. What condition
The Handover left your partner in, honestly, including what
will break first. Review your team and individual progress across
the project (
B2.3) — what worked in your collaboration, what failed, and what you learned about software teamwork. Then the pathways reflection (D4.3): research and describe a postsecondary pathway you are considering (such as university computer science, software engineering, computer engineering, or college software development) and the careers associated with computer studies that excite you (systems analyst, site reliability engineer, software architect, machine learning researcher), along with the preparation they require. - Where I stand on the Essential Skills. The Ontario Skills Passport names a set of skills and work habits that every kind of employment and study runs on; the ones this course leans on hardest are reading text, writing, document use, computer use, thinking (problem solving and decision making), working with others, and continuous learning. Take three of them — not all seven, and not the three you are best at. For each one, say where you were in where you started, where you are now, and cite the dated evidence for both: an entry, a commit, a review, a thing that went wrong. Then name the one you would work on next and what you would do about it. This section is marked on the evidence you cite and the reasoning you build from it. It is not marked on how highly or how harshly you rate yourself, and a rating with nothing under it scores nothing either way.
Do not write it as a thank-you card
The temptation is to perform gratitude and round everything up. Resist it. The reflections worth reading include the concept that never clicked, the feature that shipped broken, the review you ignored and should not have, the part of the handover you know is thin. You have a course’s worth of evidence that honesty is what makes this writing good. Trust it one last time.
Curriculum connection
B2.3
reflect on, and assess, team and individual progress during the project review.
Link to original
D4.3
research and describe careers associated with computer studies (e.g., computer scientist, software engineer, systems analyst), and the postsecondary education required to prepare for them;
Link to original
D4.4
evaluate their own development of Essential Skills and work habits that are important for success in computer studies, as identified in the Ontario Skills Passport.
Link to original