Once the journal habit exists, the question is quality — and quality comes down to one word: specific. A strong entry could only have been written by you, about this program, on this day. A weak one could have been written by anyone, about any programming class, from the hallway.
Side by side
| Weak | Strong |
|---|---|
| ”My program didn’t work." | "It crashed on line 6 of attendance.py with a ZeroDivisionError — an empty session list, passed in from my file two frames up." |
| "We used a dictionary." | "Switched the roster to a dictionary keyed by member ID. Rejected: sorted list plus binary search, because we insert far more often than we search." |
| "Code review went fine." | "Priya said spaces_left could return a negative number. I said the caller would never overbook. She wrote a test that overbooked it. She was right." |
| "I read the old code." | "Spent twenty minutes lost in report.py, then ran git log on it — a commit from March says the odd rounding is what the partner asked for. The comment was in the history, not the file." |
| "Group work went fine." | "I wrote the queue class and Dev wrote the export. Neither of us has read the other’s. That is a problem and I am raising it Thursday." |
| "Coding is hard." | "I can write recursion but I still cannot read it. I have to draw the stack every time, and other people seem not to.” |
Read the weak column: nothing happened in it. The strong column is the same day, remembered properly — a file, a line, a rejected alternative, a sentence somebody actually said. And notice the strong versions are barely longer. Specific is not the same as long.
The rejected option is the part nobody else can recover
Six months from now, the code will still show what you chose. The history will show when. The only thing that will be gone is what else was on the table and why you turned it down — and that is precisely what somebody maintaining your program needs, and precisely what The Handover asks you to defend.
So the shape to aim for is small and repeatable:
Chose X over Y and Z, because [one reason a teammate could disagree with]. If [condition] ever changes, Y becomes the better option.
That last clause is the professional move. It tells the next person what would have to be true for them to redo your decision, which is kinder than pretending it was obvious.
Feelings are welcome, anchored to a moment
The journal is not a lab report. Frustrated, proud, defensive, and relieved all belong in it. The rule is that a feeling arrives attached to the moment that caused it. “I felt stupid” floats free and teaches you nothing later. “I got defensive when Priya found the bug in my function, then spent the walk home realising I would rather she found it than the partner did” is a feeling with an address and an exit — and it is the entry you will want when Showing Growth comes looking for evidence.