Once the journal habit exists, the next question is quality — and quality in an entry 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 when I typed nothing — int() cannot turn an empty string into a number." |
| "It worked." | "The guessing game runs, but only because I copied the while line. I could not rewrite it from scratch yet." |
| "Coding is hard." | "I can write an if on its own, but nesting one inside a loop scrambles me — I lose track of which line belongs to which indent." |
| "Group work went fine." | "Avery typed most of it and I spotted the missing quote. Next time I want the keyboard for the loop part." |
| "Talked to my client." | "She said ‘I always get it wrong once’ — turns out the error is duplicate names, not counting. I was building the wrong thing.” |
Read the weak column: nothing happened in it. The strong column is the same day, remembered properly — a line number, an error, a cause, a sentence somebody actually said. And notice that the strong versions are barely longer. Specific is not the same as long; it is the difference between “it broke” and a bug you could reproduce, which is exactly what the “what broke” prompt in Code Journal is asking for.
Feelings are welcome, anchored to a moment
The journal is not a lab report. Frustrated, proud, embarrassed, and
delighted all belong in it. The rule is that a feeling arrives
attached to the moment that caused it and the code involved. “I felt
stupid” floats free and teaches you nothing later. “I felt stupid when
the same SyntaxError came back four runs in a row, so I finally read
the whole message and found the bug was on the line above” is a
feeling with an address and an exit.
The feeling is real data about you; the error is the handle you can turn. Pairing them is exactly what Mistakes Are Data argues staying curious depends on.